LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Tejun Heo <htejun@gmail.com>
Cc: Michael Tokarev <mjt@tls.msk.ru>,
Linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Vendor field with USB, [SP]ATA etc-attached disks
Date: Tue, 12 Sep 2006 21:22:59 -0400 [thread overview]
Message-ID: <45075D73.5030005@garzik.org> (raw)
In-Reply-To: <4506AB4B.9010801@gmail.com>
Tejun Heo wrote:
> For the time being, we'll have to live with boilerplate ATA vendor and
> truncated vendor ID. There are plans to make libata independent from
Truncated model ID, I presume you mean.
> SCSI which should solve the problem but it will take quite some time.
Since ATA does not distinguish between vendor and model, you can't
really solve the problem. Two high volume disk vendors don't bother to
put a vendor name in the model string at all.
Jeff
next prev parent reply other threads:[~2006-09-13 1:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-11 18:08 Michael Tokarev
2006-09-11 19:34 ` Jeff Garzik
2006-09-12 12:42 ` Tejun Heo
2006-09-13 1:22 ` Jeff Garzik [this message]
2006-09-13 1:28 ` Tejun Heo
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=45075D73.5030005@garzik.org \
--to=jeff@garzik.org \
--cc=htejun@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mjt@tls.msk.ru \
--subject='Re: Vendor field with USB, [SP]ATA etc-attached disks' \
/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
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).