[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.44L0.1102061022410.20379-100000@netrider.rowland.org>
Date: Sun, 6 Feb 2011 10:23:54 -0500 (EST)
From: Alan Stern <stern@...land.harvard.edu>
To: "Rafael J. Wysocki" <rjw@...k.pl>
cc: Minchan Kim <minchan.kim@...il.com>,
linux kernel mailing list <linux-kernel@...r.kernel.org>,
Greg Kroah-Hartman <gregkh@...e.de>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [BUG] usb_set_device_state
On Sun, 6 Feb 2011, Rafael J. Wysocki wrote:
> On Sunday, February 06, 2011, Minchan Kim wrote:
> > When I am googling, I found https://lkml.org/lkml/2011/1/14/440.
> > Maybe the bug is caused by that.
> > It is in linux-next and mmotm, not linus tree.
>
> Yes, it is, thanks!
>
> I'll revert the patch for now and see how it can be fixed.
Sorry, I didn't mention this because I thought it was obvious. Before
that patch, device_set_wakeup_capable() was a simple assignment that
could run in any context. After the patch it requires process context.
Alan Stern
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists