From: Aaron Lu <aaron.lu@intel.com>
To: Alan Stern <stern@rowland.harvard.edu>,
Jens Axboe <axboe@kernel.dk>,
James Bottomley <James.Bottomley@hansenpartnership.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
linux-pm@vger.kernel.org, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org,
Aaron Lu <aaron.lwe@gmail.com>, Shane Huang <shane.huang@amd.com>
Subject: Re: [PATCH v10 0/4] block layer runtime pm
Date: Thu, 21 Feb 2013 17:19:34 +0800 [thread overview]
Message-ID: <20130221091934.GA8612@aaronlu.sh.intel.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1302201042400.1671-100000@iolanthe.rowland.org>
On Wed, Feb 20, 2013 at 10:43:50AM -0500, Alan Stern wrote:
> On Wed, 20 Feb 2013, Aaron Lu wrote:
>
> > In August 2010, Jens and Alan discussed about "Runtime PM and the block
> > layer". http://marc.info/?t=128259108400001&r=1&w=2
> > And then Alan has given a detailed implementation guide:
> > http://marc.info/?l=linux-scsi&m=133727953625963&w=2
>
> > v10:
> > - Add link of Alan Stern's ideas on block layer runtime PM to patch 2
> > and 3's changelog;
> > - Add back code to schdule device suspend if scsi driver return -EBUSY.
>
> This all looks okay now. You can add
>
> Acked-by: Alan Stern <stern@rowland.harvard.edu>
>
> to each of the patches.
Great, thanks a lot for your kind help.
Hi James,
Can I have your ack for patch 1 and 4?
And Jens,
Do you have any comments for this series?
Thanks,
Aaron
prev parent reply other threads:[~2013-02-21 9:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-20 6:11 [PATCH v10 0/4] block layer runtime pm Aaron Lu
2013-02-20 6:11 ` [PATCH v10 1/4] block: add a flag to identify PM request Aaron Lu
2013-02-20 6:11 ` [PATCH v10 2/4] block: add runtime pm helpers Aaron Lu
2013-02-20 6:11 ` [PATCH v10 3/4] block: implement runtime pm strategy Aaron Lu
2013-02-20 6:11 ` [PATCH v10 4/4] sd: change to auto suspend mode Aaron Lu
2013-02-20 15:43 ` [PATCH v10 0/4] block layer runtime pm Alan Stern
2013-02-21 9:19 ` Aaron Lu [this message]
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=20130221091934.GA8612@aaronlu.sh.intel.com \
--to=aaron.lu@intel.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=aaron.lwe@gmail.com \
--cc=axboe@kernel.dk \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=shane.huang@amd.com \
--cc=stern@rowland.harvard.edu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).