From: Jeff Garzik <jeff@garzik.org>
To: Tejun Heo <htejun@gmail.com>
Cc: Robert Hancock <hancockr@shaw.ca>,
Andrew Morton <akpm@linux-foundation.org>,
enricoss@tiscali.it, linux-kernel@vger.kernel.org,
linux-ide@vger.kernel.org
Subject: Re: [PATCH 2.6.22-rc5] libata: add HTS541616J9SA00 to NCQ blacklist
Date: Mon, 02 Jul 2007 10:14:58 -0400 [thread overview]
Message-ID: <46890862.2090002@garzik.org> (raw)
In-Reply-To: <467F286B.40607@gmail.com>
Tejun Heo wrote:
> Another member of HTS5416* family doing spurious NCQ completion.
>
> Signed-off-by: Tejun Heo <htejun@gmail.com>
> Cc: Enrico Sardi <enricoss@tiscali.it>
> ---
> drivers/ata/libata-core.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/ata/libata-core.c b/drivers/ata/libata-core.c
> index adfae9d..fbca8d8 100644
> --- a/drivers/ata/libata-core.c
> +++ b/drivers/ata/libata-core.c
> @@ -3803,6 +3803,7 @@ static const struct ata_blacklist_entry ata_device_blacklist [] = {
> /* Drives which do spurious command completion */
> { "HTS541680J9SA00", "SB2IC7EP", ATA_HORKAGE_NONCQ, },
> { "HTS541612J9SA00", "SBDIC7JP", ATA_HORKAGE_NONCQ, },
> + { "Hitachi HTS541616J9SA00", "SB4OC70P", ATA_HORKAGE_NONCQ, },
> { "WDC WD740ADFD-00NLR1", NULL, ATA_HORKAGE_NONCQ, },
applied
prev parent reply other threads:[~2007-07-02 14:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.sspu6LOivd/touNtS2IsMKPqHa0@ifi.uio.no>
[not found] ` <fa.19XJG1Asdp1zwcWLxolIH6F+5lY@ifi.uio.no>
2007-06-24 19:42 ` hsm violation Robert Hancock
2007-06-25 2:12 ` Tejun Heo
2007-06-25 2:28 ` [PATCH 2.6.22-rc5] libata: add HTS541616J9SA00 to NCQ blacklist Tejun Heo
2007-06-25 2:39 ` Robert Hancock
2007-06-25 2:49 ` Tejun Heo
2007-06-25 3:47 ` Petr Vandrovec
2007-06-25 4:05 ` Tejun Heo
2007-06-25 4:10 ` Robert Hancock
2007-06-25 4:22 ` Petr Vandrovec
2007-06-25 4:29 ` Tejun Heo
2007-07-02 7:12 ` Tejun Heo
2007-07-02 14:14 ` Jeff Garzik [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=46890862.2090002@garzik.org \
--to=jeff@garzik.org \
--cc=akpm@linux-foundation.org \
--cc=enricoss@tiscali.it \
--cc=hancockr@shaw.ca \
--cc=htejun@gmail.com \
--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).