From: Jeff Garzik <jeff@garzik.org>
To: Chuck Ebbert <cebbert@redhat.com>
Cc: IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: Another Maxtor drive with broken NCQ
Date: Sat, 07 Jul 2007 10:51:14 -0400 [thread overview]
Message-ID: <468FA862.6030701@garzik.org> (raw)
In-Reply-To: <468E9469.4090007@redhat.com>
Chuck Ebbert wrote:
> On 07/06/2007 03:09 PM, Jeff Garzik wrote:
>>> {"Maxtor 6B200M0", "BANC1BM0", ATA_HORKAGE_NONCQ }
>>>
>>> Or should *all* Maxtor 6B200M0 be blacklisted, since there's already
>>> one of them in the list?
>> Wanna send that as a patch, with attribution and sign-offs? :)
>>
>
> For all revisions, or just that one new one?
I don't think all 6B200M0 should be blacklisted, but BANC* is probably
bad. I don't think the code can do wildcard matching, so just the one
revision is probably the best we can do at the moment.
Jeff
next prev parent reply other threads:[~2007-07-07 14:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-06 18:45 Another Maxtor drive with broken NCQ Chuck Ebbert
2007-07-06 19:09 ` Jeff Garzik
2007-07-06 19:13 ` Chuck Ebbert
2007-07-07 14:51 ` Jeff Garzik [this message]
2007-07-07 20:29 ` Alan Cox
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=468FA862.6030701@garzik.org \
--to=jeff@garzik.org \
--cc=cebbert@redhat.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).