Re: [RFC PATCH 0/5] add gpio_chip_ops to hold GPIO operations

[Arnd Bergmann]

On Tuesday 22 April 2014, Javier Martinez Canillas wrote:
> Hello Linus,
> 
> On Tue, Apr 22, 2014 at 1:36 PM, Linus Walleij <linus.walleij@xxxxxxxxxx> wrote:
> > On Tue, Apr 8, 2014 at 8:20 PM, Javier Martinez Canillas
> > <javier.martinez@xxxxxxxxxxxxxxx> wrote:
> >
> >> So this is an RFC patch-set to add a virtual table to be used by
> >> GPIO chip controllers and consist of the following patches:
> >
> > Overall I like this.

Agreed, it's a very good cleanup.

> > However I don't want to see any transitional phase. I prefer a BIG
> > fat patch converting everyone and its dog to the new vtable and
> > removing the old function pointers. This can be based on the HEAD
> > of my GPIO devel branch.
> >
> 
> Ok, I was adding a commit per GPIO driver but the patch-set would have
> been very big (~200 patches).
> 
> > It may be a good idea to use coccinelle for this refactoring in order
> > not to miss any users.
> >
> 
> Agreed, I was manually searching for users by using grep but I agree
> that is much safer to use coccinelle for this. I don't have previous
> experience writing coccinelle semantics patches though so it may take
> more time than I thought but it is the perfect excuse to finally learn
> how to do it :-)

I'm not a big fan of doing this all at once, but it's not my call here.
Just one recommendation: if you can't do an obvious coccinelle patch
to do everything at once, use extra patches in the beginning to clean
up the code enough to make it work, then have the large patch fully
automated.

	Arnd
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/