From: Daniel Drake <dsd@gentoo.org>
To: Tejun Heo <htejun@gmail.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: Fixing halt/shutdown for libata spindown handling
Date: Wed, 16 May 2007 21:16:05 -0400 [thread overview]
Message-ID: <464BACD5.3030003@gentoo.org> (raw)
In-Reply-To: <46496D47.9010504@gmail.com>
Hi Tejun,
Thanks for the fast response and action.
Tejun Heo wrote:
> it. I'll come up with a patch, please wait a bit before releasing the
> update.
The patch has been merged into libata-dev.git so I'd like to revisit
this topic now.
Am I right in saying, to fix 2.6.21, the following patches are needed,
and no others, in this order:
sd: fix return value of sd_sync_cache()
3721050afc6cb6ddf6de0f782e2054ebcc225e9b
(not sure if this one is required?)
[SCSI] sd: implement START/STOP management
3c94c5a2fb43a654e777f509d5032b0db8ed09f
libata: reimplement suspend/resume support using sdev->manage_start_stop
9666f4009c22f6520ac3fb8a19c9e32ab973e828
libata: implement libata.spindown_compat
920a4b1038e442700a1cfac77ea7e20bd615a2c3
libata: fix shutdown warning message printing
da071b42f73dabbd0daf7ea4c3ff157d53b00648
libata: track spindown status and skip spindown_compat if possible
13b8d09f5de0aaa3153bbccc98baf247387823dc
Additionally, no userspace modifications are needed, at least while
Gentoo's shutdown/halt programs are not attempting to spin down libata
disks?
I note that the patch titled "SCSI: kill sht->suspend/resume" (not
included in the above tree) is not yet merged into Linus' tree. Am I
right in saying it's not required for the disk spindown stuff to work
properly?
Thanks!
Daniel
next prev parent reply other threads:[~2007-05-17 1:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-15 3:29 Fixing halt/shutdown for libata spindown handling Daniel Drake
2007-05-15 8:20 ` Tejun Heo
2007-05-15 10:31 ` Francesco Pretto
2007-05-15 10:42 ` Tejun Heo
2007-05-17 1:16 ` Daniel Drake [this message]
2007-05-17 15:27 ` Tejun Heo
2007-05-29 22:42 ` Daniel Drake
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=464BACD5.3030003@gentoo.org \
--to=dsd@gentoo.org \
--cc=htejun@gmail.com \
--cc=linux-ide@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.