Re: [PATCH 5/5] gpiolib: separation of pin concerns

2012-11-06 Thread Stephen Warren
On 11/06/2012 08:17 AM, Linus Walleij wrote: > From: Linus Walleij > > The fact that of_gpiochip_add_pin_range() and > gpiochip_add_pin_range() share too much code is fragile and > will invariably mean that bugs need to be fixed in two places > instead of one. > > So separate the concerns of gpi

[PATCH 5/5] gpiolib: separation of pin concerns

2012-11-06 Thread Linus Walleij
From: Linus Walleij The fact that of_gpiochip_add_pin_range() and gpiochip_add_pin_range() share too much code is fragile and will invariably mean that bugs need to be fixed in two places instead of one. So separate the concerns of gpiolib.c and gpiolib-of.c and have the latter call the former a