The patch titled drivers/leds/ledtrig-timer.c: fix broken sysfs delay handling has been removed from the -mm tree. Its filename was leds-ledtrig-timer-fix-broken-sysfs-delay-handling.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/ledtrig-timer.c: fix broken sysfs delay handling From: Johan Hovold <jhovold@xxxxxxxxx> Fix regression introduced by commit 5ada28bf7675 ("led-class: always implement blinking") which broke sysfs delay handling by not storing the updated value. Consequently it was only possible to set one of the delays through the sysfs interface as the other delay was automatically restored to it's default value. Reading the parameters always gave the defaults. Signed-off-by: Johan Hovold <jhovold@xxxxxxxxx> Acked-by: Florian Fainelli <florian@xxxxxxxxxxx> Acked-by: Richard Purdie <richard.purdie@xxxxxxxxxxxxxxxxxxx> Cc: <stable@xxxxxxxxxx> [2.6.37+] Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- drivers/leds/ledtrig-timer.c | 2 ++ 1 file changed, 2 insertions(+) diff -puN drivers/leds/ledtrig-timer.c~leds-ledtrig-timer-fix-broken-sysfs-delay-handling drivers/leds/ledtrig-timer.c --- a/drivers/leds/ledtrig-timer.c~leds-ledtrig-timer-fix-broken-sysfs-delay-handling +++ a/drivers/leds/ledtrig-timer.c @@ -41,6 +41,7 @@ static ssize_t led_delay_on_store(struct if (count == size) { led_blink_set(led_cdev, &state, &led_cdev->blink_delay_off); + led_cdev->blink_delay_on = state; ret = count; } @@ -69,6 +70,7 @@ static ssize_t led_delay_off_store(struc if (count == size) { led_blink_set(led_cdev, &led_cdev->blink_delay_on, &state); + led_cdev->blink_delay_off = state; ret = count; } _ Patches currently in -mm which might be from jhovold@xxxxxxxxx are origin.patch linux-next.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