This is a note to let you know that I've just added the patch titled
USB: Realtek cr: fix autopm scheduling while atomic
to the 3.2-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
usb-realtek-cr-fix-autopm-scheduling-while-atomic.patch
and it can be found in the queue-3.2 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree,
please let <[email protected]> know about it.
>From b3ef051db763b640d1ff724b616ffba940896b44 Mon Sep 17 00:00:00 2001
From: Stanislaw Gruszka <[email protected]>
Date: Thu, 26 Jan 2012 12:29:42 +0100
Subject: USB: Realtek cr: fix autopm scheduling while atomic
From: Stanislaw Gruszka <[email protected]>
commit b3ef051db763b640d1ff724b616ffba940896b44 upstream.
Resolves:
https://bugzilla.redhat.com/show_bug.cgi?id=784345
Reported-by: Francis Moreau <[email protected]>
Reported-and-tested-by: Christian D <[email protected]>
Reported-and-tested-by: Jimmy Dorff <[email protected]>
Reported-and-tested-by: [email protected]
Signed-off-by: Stanislaw Gruszka <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>
---
drivers/usb/storage/realtek_cr.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/drivers/usb/storage/realtek_cr.c
+++ b/drivers/usb/storage/realtek_cr.c
@@ -791,7 +791,7 @@ static void rts51x_suspend_timer_fn(unsi
rts51x_set_stat(chip, RTS51X_STAT_SS);
/* ignore mass storage interface's children */
pm_suspend_ignore_children(&us->pusb_intf->dev, true);
- usb_autopm_put_interface(us->pusb_intf);
+ usb_autopm_put_interface_async(us->pusb_intf);
US_DEBUGP("%s: RTS51X_STAT_SS 01,"
"intf->pm_usage_cnt:%d, power.usage:%d\n",
__func__,
Patches currently in stable-queue which might be from [email protected] are
queue-3.2/usb-realtek-cr-fix-autopm-scheduling-while-atomic.patch
queue-3.2/brcmsmac-fix-tx-queue-flush-infinite-loop.patch
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
