Wow!! So many replies, let me reply to everyone in this chain. On 18 June 2013 22:05, Olof Johansson <olof@xxxxxxxxx> wrote: > On Tue, Jun 18, 2013 at 9:11 AM, Marc Zyngier <marc.zyngier@xxxxxxx> wrote: >> On 18/06/13 16:42, Guenter Roeck wrote: >>> On Tue, Jun 18, 2013 at 08:50:25PM +0530, Viresh Kumar wrote: >>>> Lets mark it broken until somebody with this hardware gets up and fixes it. >>>> >>> I must be missing something. What is the point of the remaining patches in this >>> case ? In case somebody wakes up and tries to fix this driver, he doesn't have to write stuff which I already wrote. That's it. This stuff was pending in my tree for more than a year now and I wanted to get rid of it (without deleting it) :) >> Indeed. This looks like pointless churn to me, unless someone actually >> picks up the driver and fixes it for good. >> >> If nobody cares enough about it, then maybe it should be moved into >> staging and eventually retired... > > > That was a year ago, and nobody has done anything to the driver. Just > remove it -- if someone wants to do the work later on it's easy to > revert the commit and start over. > > Keeping code in the kernel but marking it BROKEN is only useful if we > think someone will fix it soon. It seems very unlikely in this case. I believed that this is the driver which will be used by all cortex family, i.e. all ARM SMP platforms, isn't it? I am sure atleast the A9 family had this. If no, then which ones are the real users of this driver/hardware? If yes, Why isn't anybody using this? I will send a patch that will delete this driver and will provide link to my patches, in case somebody wants it back in future. -- Viresh -- To unsubscribe from this list: send the line "unsubscribe linux-watchdog" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
