From: Jeff Garzik <jeff@garzik.org>
To: Robert Hancock <hancockr@shaw.ca>
Cc: linux-kernel <linux-kernel@vger.kernel.org>, linux-ide@vger.kernel.org
Subject: Re: [PATCH] libata: fix translation for START STOP UNIT
Date: Tue, 30 Jan 2007 09:24:37 -0500 [thread overview]
Message-ID: <45BF5525.5040709@garzik.org> (raw)
In-Reply-To: <45BD4E0A.7060501@shaw.ca>
Robert Hancock wrote:
> Applies to 2.6.20-rc6.
>
> ---
>
> libata's SCSI translation for the SCSI START STOP UNIT command with the
> START bit clear (i.e. stopping the drive) appears to be incorrect. It
> sends an ATA STANDBY command with the time period set to 0, which the
> code comment says means "now", but the ATA standard says this means
> disable the standby timer, which effectively does nothing. Change this
> to issue a STANDBY IMMEDIATE command which will actually spin the drive
> down. The SAT (SCSI/ATA Translation) standard revision 9 concurs with
> this choice.
>
> Signed-off-by: Robert Hancock <hancockr@shaw.ca>
FWIW, I am having to apply Andrew Morton's version of your patches,
because your patch form isn't quite right. Review
Documentation/SubmittingPatches and http://linux.yyz.us/patch-format.html
Most notably:
* Your patch description follows the "---" terminator, which is
precisely the opposite of what should happen. In the correct form, any
comments such as "Applies to 2.6.20-rc6" should follow the "---"
terminator, which in turn follows the patch description and signoff.
* Include the patch inline rather than as an attachment. Even a
text/plain attachment is very difficult to review and quote in popular
email programs.
Jeff
next prev parent reply other threads:[~2007-01-30 14:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-29 1:29 [PATCH] libata: fix translation for START STOP UNIT Robert Hancock
2007-01-30 14:24 ` Jeff Garzik [this message]
2007-01-30 14:36 ` Robert Hancock
2007-01-30 14:43 ` Jeff Garzik
2007-01-31 8:22 ` Martin J. Bligh
2007-01-31 0:38 ` Mark Lord
2007-02-01 0:27 ` Tejun Heo
2007-02-01 1:04 ` Mark Lord
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=45BF5525.5040709@garzik.org \
--to=jeff@garzik.org \
--cc=hancockr@shaw.ca \
--cc=linux-ide@vger.kernel.org \
--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 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).