From: Tejun Heo <htejun@gmail.com>
To: Petr Vandrovec <vandrove@vc.cvut.cz>
Cc: Robert Hancock <hancockr@shaw.ca>, Jeff Garzik <jeff@garzik.org>,
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, 25 Jun 2007 13:29:15 +0900 [thread overview]
Message-ID: <467F449B.1040200@gmail.com> (raw)
In-Reply-To: <467F42F3.1000609@vc.cvut.cz>
Petr Vandrovec wrote:
>>> Hmmm... The last one (HTS541612J9SA00) is taken directly from hdparm
>>> output, and I think I verified the patch with the reporter. Hmm... Can
>>> anyone verify these module strings?
>>
>> Could well be that they've started attaching Hitachi to the ID strings
>> now.. In the past it hasn't seemed to have been Hitachi's (and IBM's
>> before that) practice to have it there, but maybe they see the
>> advantage of being able to figure out who made the drive now :-)
>
> Perhaps ones sold directly by Hitachi are Hitachi, while ones sold
> through OEMs are no-name?
I dunno but I doubt they care that much about the model string but one
way or the other we might have to do pattern matching on HTS541* anyway.
--
tejun
next prev parent reply other threads:[~2007-06-25 4:29 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 [this message]
2007-07-02 7:12 ` Tejun Heo
2007-07-02 14:14 ` Jeff Garzik
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=467F449B.1040200@gmail.com \
--to=htejun@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=enricoss@tiscali.it \
--cc=hancockr@shaw.ca \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vandrove@vc.cvut.cz \
/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).