The patch titled
leds: fix locking for WM8350
has been added to the -mm tree. Its filename is
leds-add-wm8350-led-driver-fix.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: leds: fix locking for WM8350
From: Mark Brown <broonie@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
LED API functions aren't allowed to sleep so we can't take a lock when
setting the brightness of the LED.
Signed-off-by: Mark Brown <broonie@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
Cc: Richard Purdie <rpurdie@xxxxxxxxxxxxxxx>
Cc: Richard Purdie <rpurdie@xxxxxxxxx>
Cc: Liam Girdwood <lrg@xxxxxxxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
drivers/leds/leds-wm8350.c | 3 ---
1 file changed, 3 deletions(-)
diff -puN drivers/leds/leds-wm8350.c~leds-add-wm8350-led-driver-fix drivers/leds/leds-wm8350.c
--- a/drivers/leds/leds-wm8350.c~leds-add-wm8350-led-driver-fix
+++ a/drivers/leds/leds-wm8350.c
@@ -170,10 +170,7 @@ static void wm8350_led_set(struct led_cl
{
struct wm8350_led *led = to_wm8350_led(led_cdev);
- mutex_lock(&led->mutex);
led->value = value;
- mutex_unlock(&led->mutex);
-
schedule_work(&led->work);
}
_
Patches currently in -mm which might be from broonie@xxxxxxxxxxxxxxxxxxxxxxxxxxx are
origin.patch
linux-next.patch
leds-add-wm8350-led-driver.patch
leds-add-wm8350-led-driver-fix.patch
mfd-correct-wm8350-i2c-return-code-usage.patch
power_supply-add-support-for-wm8350-pmu.patch
power_supply-add-support-for-wm8350-pmu-update.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
