From: Aaron Lu <aaron.lu@intel.com>
To: "James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>,
Alan Stern <stern@rowland.harvard.edu>,
Jeff Garzik <jgarzik@pobox.com>
Cc: linux-scsi@vger.kernel.org, linux-pm@vger.kernel.org,
Aaron Lu <aaron.lwe@gmail.com>, Aaron Lu <aaron.lu@intel.com>
Subject: [PATCH 0/3] may_power_off for scsi device
Date: Thu, 30 Aug 2012 14:43:57 +0800 [thread overview]
Message-ID: <1346309040-27112-1-git-send-email-aaron.lu@intel.com> (raw)
Add a new flag may_power_off for scsi device to let user control when
it is runtime suspended, can we remove its power.
This patchset makes the following patch sent previously deprecated:
[PATCH] scsi: sr: add may_power_off flag
http://marc.info/?l=linux-scsi&m=134614323832520&w=2
The patch "scsi: pm: add may_power_off flag" also appears in another
patchset intended for libata due to libata will use this flag to
decide if ACPI D3cold can be used. They two patches are identical.
Based on top of the previously sent v4 ZPODD patchset:
https://lkml.org/lkml/2012/7/27/71
Aaron Lu (3):
scsi: pm: add may_power_off flag
scsi: sr: use may_power_off to enable/disable ZPODD
scsi: sd: add may_power_off sysfs entry
drivers/scsi/sd.c | 34 ++++++++++++++++++++++++++++
drivers/scsi/sr.c | 55 +++++++++++++++++++++++++++++++++++++++++-----
include/scsi/scsi_device.h | 1 +
3 files changed, 84 insertions(+), 6 deletions(-)
--
1.7.11.5
next reply other threads:[~2012-08-30 6:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-30 6:43 Aaron Lu [this message]
2012-08-30 6:43 ` [PATCH 1/3] scsi: pm: add may_power_off flag Aaron Lu
2012-08-30 14:24 ` Alan Stern
2012-08-31 11:39 ` Aaron Lu
2012-08-30 6:43 ` [PATCH 2/3] scsi: sr: use may_power_off to enable/disable ZPODD Aaron Lu
2012-08-30 6:44 ` [PATCH 3/3] scsi: sd: add may_power_off sysfs entry Aaron Lu
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=1346309040-27112-1-git-send-email-aaron.lu@intel.com \
--to=aaron.lu@intel.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=aaron.lwe@gmail.com \
--cc=jgarzik@pobox.com \
--cc=linux-pm@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--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).