From: Jeff Garzik <jeff@garzik.org>
To: Tejun Heo <htejun@gmail.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: [PATCH #upstream] libata: update spurious NCQ completion blacklist
Date: Sat, 29 Sep 2007 02:23:37 -0400 [thread overview]
Message-ID: <46FDEF69.7090506@garzik.org> (raw)
In-Reply-To: <46FD01B3.9030700@gmail.com>
Tejun Heo wrote:
> * The firmware version of ST3160812AS is "3.ADJ" no "3.AD".
> * Add several entries from various sources.
>
> Signed-off-by: Tejun Heo <htejun@gmail.com>
> ---
> drivers/ata/libata-core.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/ata/libata-core.c b/drivers/ata/libata-core.c
> index fd4563d..7f424c4 100644
> --- a/drivers/ata/libata-core.c
> +++ b/drivers/ata/libata-core.c
> @@ -3891,9 +3891,12 @@ static const struct ata_blacklist_entry ata_device_blacklist [] = {
> { "HTS541612J9SA00", "SBDIC7JP", ATA_HORKAGE_NONCQ, },
> { "Hitachi HTS541616J9SA00", "SB4OC70P", ATA_HORKAGE_NONCQ, },
> { "WDC WD740ADFD-00NLR1", NULL, ATA_HORKAGE_NONCQ, },
> + { "WDC WD3200AAJS-00RYA0", "12.01B01", ATA_HORKAGE_NONCQ, },
> { "FUJITSU MHV2080BH", "00840028", ATA_HORKAGE_NONCQ, },
> + { "ST9120822AS", "3.CLF", ATA_HORKAGE_NONCQ, },
> { "ST9160821AS", "3.CLF", ATA_HORKAGE_NONCQ, },
> - { "ST3160812AS", "3.AD", ATA_HORKAGE_NONCQ, },
> + { "ST3160812AS", "3.ADJ", ATA_HORKAGE_NONCQ, },
> + { "ST980813AS", "3.ADB", ATA_HORKAGE_NONCQ, },
> { "SAMSUNG HD401LJ", "ZZ100-15", ATA_HORKAGE_NONCQ, },
applied
prev parent reply other threads:[~2007-09-29 6:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-28 13:29 [PATCH #upstream] libata: update spurious NCQ completion blacklist Tejun Heo
2007-09-29 6:23 ` 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=46FDEF69.7090506@garzik.org \
--to=jeff@garzik.org \
--cc=alan@lxorguk.ukuu.org.uk \
--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 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).