Messages in this thread | | | Date | Wed, 9 Mar 2011 13:45:04 -0800 | From | Andrew Morton <> | Subject | Re: [PATCH, RESEND] Putting the device into runtime suspend after resume()/probe() is handled |
| |
On Wed, 09 Mar 2011 12:39:34 +0000 Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> From: Alan Cox <alan@lxorguk.ukuu.org.uk> > To: akpm@linux-foundation.org, linux-kernel@vger.kernel.org > Subject: [PATCH, RESEND] Putting the device into runtime suspend after resume()/probe() is handled > Date: Wed, 09 Mar 2011 12:39:34 +0000 > User-Agent: StGIT/0.14.3 > > From: Hong Liu <hong.liu@intel.com> > > by the PM core and the device core code. No need to manually add them in > each single driver. And correct the runtime state in remove(). > > Signed-off-by: Hong Liu <hong.liu@intel.com> > Signed-off-by: Alan Cox <alan@linux.intel.com>
I'd merged this a while back but was awaiting info on why v1 had a cc:stable so the changelog could be updated to indicate why a -stable backport was needed.
I see that the cc:stable has been removed so that settles that. But it's still unclear how serious the bugs-which-were fixed are. Oh well, a bug's a bug. I put it in my 2.6.38 queue anyway.
| |