From: Tejun Heo <htejun@gmail.com>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Jeff Garzik <jeff@garzik.org>,
linux-ide@vger.kernel.org, linux-scsi@vger.kernel.org,
djwong@us.ibm.com, hmh@hmh.eng.br
Subject: Re: [PATCH 2/3] sd: implement START/STOP management
Date: Wed, 21 Mar 2007 02:08:11 +0900 [thread overview]
Message-ID: <460014FB.1050703@gmail.com> (raw)
In-Reply-To: <1174409899.3522.16.camel@mulgrave.il.steeleye.com>
James Bottomley wrote:
> On Wed, 2007-03-21 at 00:13 +0900, Tejun Heo wrote:
>> Implement SBC START/STOP management. sdev->mange_start_stop is added.
>> When it's set to one, sd STOPs the device on suspend and shutdown and
>> STARTs it on resume. sdev->manage_start_stop defaults is in sdev
>> instead of scsi_disk cdev to allow ->slave_config() override the
>> default configuration but is exported under scsi_disk sysfs node as
>> sdev->allow_restart is.
>>
>> When manage_start_stop is zero (the default value), this patch doesn't
>> introduce any behavior change.
>
> I have this in scsi-misc-2.6. There was a minor space before tab no-no
> which git complained about (and I fixed). Unfortunately, there's a
> pretty major merge conflict with prior sd.c patches in scsi-misc-2.6.
> I've merged and fixed this but it's going to create a bit of a
> difficulty for applying the libata pieces.
I got too comfortable with libata-dev#upstream and forgot to verify
patches against scsi-misc-2.6. Sorry about that. If you don't have
objection against the content, I'll resubmit the SCSI part against
scsi-misc-2.6. Once it's in scsi-misc-2.6, we can pull it into
libata-dev#upstream and do the libata part there. As the SCSI change
doesn't break libata, they can be done separately.
Thanks.
--
tejun
next prev parent reply other threads:[~2007-03-20 17:08 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-20 15:07 [PATCH 1/3] sd: fix return value of sd_sync_cache() Tejun Heo
2007-03-20 15:13 ` [PATCH 2/3] sd: implement START/STOP management Tejun Heo
2007-03-20 15:25 ` [PATCH 3/4] libata: reimplement suspend/resume support using sdev->manage_start_stop Tejun Heo
2007-03-20 15:29 ` Christoph Hellwig
2007-03-21 7:05 ` [PATCH scsi-misc-2.6] SCSI: kill sht->suspend/resume Tejun Heo
2007-03-21 14:19 ` Christoph Hellwig
2007-03-21 15:16 ` James Bottomley
2007-05-14 15:52 ` Tejun Heo
2007-03-20 15:55 ` [PATCH 4/4] libata: implement libata.spindown_compat Tejun Heo
2007-04-17 14:45 ` Jeff Garzik
2007-04-17 15:01 ` James Bottomley
2007-04-17 15:20 ` Jeff Garzik
2007-04-17 15:26 ` James Bottomley
2007-04-17 17:09 ` Tejun Heo
2007-04-17 17:33 ` James Bottomley
2007-03-20 16:39 ` [PATCH 3/4] libata: reimplement suspend/resume support using sdev->manage_start_stop Alan Cox
2007-03-20 16:15 ` Oliver Neukum
2007-03-20 16:58 ` [PATCH 2/3] sd: implement START/STOP management James Bottomley
2007-03-20 17:08 ` Tejun Heo [this message]
2007-03-20 17:26 ` James Bottomley
2007-03-21 3:42 ` Tejun Heo
2007-03-20 17:58 ` Douglas Gilbert
2007-03-20 18:41 ` James Bottomley
2007-03-21 2:35 ` Tejun Heo
2007-03-22 10:21 ` Vladislav Bolkhovitin
2007-03-22 12:29 ` Henrique de Moraes Holschuh
2007-03-22 15:14 ` Vladislav Bolkhovitin
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=460014FB.1050703@gmail.com \
--to=htejun@gmail.com \
--cc=James.Bottomley@SteelEye.com \
--cc=djwong@us.ibm.com \
--cc=hmh@hmh.eng.br \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-scsi@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 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).