From: Andrew Morton <akpm@linux-foundation.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org, Hong Liu <hong.liu@intel.com>
Subject: Re: [PATCH, RESEND] Putting the device into runtime suspend after resume()/probe() is handled
Date: Wed, 9 Mar 2011 13:45:04 -0800 [thread overview]
Message-ID: <20110309134504.6d850802.akpm@linux-foundation.org> (raw)
In-Reply-To: <20110309123916.19908.78417.stgit@bob.linux.org.uk>
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.
next prev parent reply other threads:[~2011-03-09 21:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-09 12:39 [PATCH, RESEND] Putting the device into runtime suspend after resume()/probe() is handled Alan Cox
2011-03-09 21:45 ` Andrew Morton [this message]
2011-03-09 21:59 ` Alan Cox
2011-03-09 22:07 ` Andrew Morton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110309134504.6d850802.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=hong.liu@intel.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.