The patch titled gpiolib: fix poll(2) support reconfigure on sysfs polarity change has been added to the -mm tree. Its filename is gpiolib-fix-poll2-support-reconfigure-on-sysfs-polarity-change.patch Before you just go and hit "reply", please: a) Consider who else should be cc'ed b) Prefer to cc a suitable mailing list as well c) Ideally: find the original patch on the mailing list and do a reply-to-all to that, adding suitable additional cc's *** Remember to use Documentation/SubmitChecklist when testing your code *** See http://userweb.kernel.org/~akpm/stuff/added-to-mm.txt to find out what to do about this The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/ ------------------------------------------------------ Subject: gpiolib: fix poll(2) support reconfigure on sysfs polarity change From: Jani Nikula <ext-jani.1.nikula@xxxxxxxxx> Previously enabled poll(2) support on one edge was never reconfigured when sysfs polarity change was triggered from kernel, because 'struct device *dev' shadowed an earlier definition. Found by sparse, which I should've run much earlier. Signed-off-by: Jani Nikula <ext-jani.1.nikula@xxxxxxxxx> Cc: David Brownell <david-b@xxxxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- drivers/gpio/gpiolib.c | 2 -- 1 file changed, 2 deletions(-) diff -puN drivers/gpio/gpiolib.c~gpiolib-fix-poll2-support-reconfigure-on-sysfs-polarity-change drivers/gpio/gpiolib.c --- a/drivers/gpio/gpiolib.c~gpiolib-fix-poll2-support-reconfigure-on-sysfs-polarity-change +++ a/drivers/gpio/gpiolib.c @@ -858,8 +858,6 @@ int gpio_sysfs_set_active_low(unsigned g desc = &gpio_desc[gpio]; if (test_bit(FLAG_EXPORT, &desc->flags)) { - struct device *dev; - dev = class_find_device(&gpio_class, NULL, desc, match_export); if (dev == NULL) { status = -ENODEV; _ Patches currently in -mm which might be from ext-jani.1.nikula@xxxxxxxxx are gpiolib-fix-poll2-support-reconfigure-on-sysfs-polarity-change.patch -- To unsubscribe from this list: send the line "unsubscribe mm-commits" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html