Re: [PATCH, RESEND] Putting the device into runtime suspend afterresume()/probe() is handled

From: Andrew Morton
Date: Wed Mar 09 2011 - 16:52:57 EST


On Wed, 09 Mar 2011 12:39:34 +0000
Alan Cox <alan@xxxxxxxxxxxxxxxxxxx> wrote:

> From: Alan Cox <alan@xxxxxxxxxxxxxxxxxxx>
> To: akpm@xxxxxxxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx
> 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@xxxxxxxxx>
>
> 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@xxxxxxxxx>
> Signed-off-by: Alan Cox <alan@xxxxxxxxxxxxxxx>

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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/