The patch titled
drivers/leds/leds-bd2802.c: bd2802_unregister_led_classdev() should unregister all registered leds
has been removed from the -mm tree. Its filename was
drivers-leds-leds-bd2802c-bd2802_unregister_led_classdev-should-unregister-all-registered-leds.patch
This patch was dropped because it was merged into mainline or a subsystem tree
The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
------------------------------------------------------
Subject: drivers/leds/leds-bd2802.c: bd2802_unregister_led_classdev() should unregister all registered leds
From: Axel Lin <axel.lin@xxxxxxxxx>
bd2802_unregister_led_classdev() should unregister all registered
instances of led_classdev class that had registered by
bd2802_register_led_classdev().
Signed-off-by: Axel Lin <axel.lin@xxxxxxxxx>
Acked-by: Kim Kyuwon <q1.kim@xxxxxxxxxxx>
Cc: Richard Purdie <rpurdie@xxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
drivers/leds/leds-bd2802.c | 5 +++++
1 file changed, 5 insertions(+)
diff -puN drivers/leds/leds-bd2802.c~drivers-leds-leds-bd2802c-bd2802_unregister_led_classdev-should-unregister-all-registered-leds drivers/leds/leds-bd2802.c
--- a/drivers/leds/leds-bd2802.c~drivers-leds-leds-bd2802c-bd2802_unregister_led_classdev-should-unregister-all-registered-leds
+++ a/drivers/leds/leds-bd2802.c
@@ -662,6 +662,11 @@ failed_unregister_led1_R:
static void bd2802_unregister_led_classdev(struct bd2802_led *led)
{
cancel_work_sync(&led->work);
+ led_classdev_unregister(&led->cdev_led2b);
+ led_classdev_unregister(&led->cdev_led2g);
+ led_classdev_unregister(&led->cdev_led2r);
+ led_classdev_unregister(&led->cdev_led1b);
+ led_classdev_unregister(&led->cdev_led1g);
led_classdev_unregister(&led->cdev_led1r);
}
_
Patches currently in -mm which might be from axel.lin@xxxxxxxxx are
origin.patch
linux-next.patch
leds-renesas-tpu-led-driver-v2-fix.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
