From: Douglas Gilbert <dougg@torque.net>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: RFC: moving drivers to a new drivers/ata directory
Date: Fri, 15 Oct 2004 18:37:13 +1000 [thread overview]
Message-ID: <416F8C39.6010804@torque.net> (raw)
In-Reply-To: <416F5757.8000306@pobox.com>
Jeff Garzik wrote:
>
> Eventually I would like to move libata, and a few non-libata driver like
> 3ware, to drivers/ata. It would appear in the makefile (and link order)
> _after_ drivers/ide and drivers/scsi.
>
> Comments/objections?
A comment: if SAS HBAs ever get installed on motherboards then
it won't be obvious to the average user which susbsystem they
should configure (i.e. ATA/SATA or SCSI/SAS). In both cases an
internal SATA disk could be connected via a SATA cable to a
plug on the motherboard.
So if you do move the drivers to the ata directory it may be
useful to stress that it is the category of HBA that is
signficant rather than the device at the far end of the cable.
Doug Gilbert
next prev parent reply other threads:[~2004-10-15 8:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-15 4:51 RFC: moving drivers to a new drivers/ata directory Jeff Garzik
2004-10-15 7:46 ` Christoph Hellwig
2004-10-15 17:22 ` Jeff Garzik
2004-10-20 15:34 ` Christoph Hellwig
2004-10-20 15:46 ` Jeff Garzik
2004-10-21 17:04 ` PATAPI via libata promise 20275 (was: RFC: moving drivers to a new drivers/ata directory) Doug Maxey
2004-10-21 17:10 ` PATAPI via libata promise 20275 Jeff Garzik
2004-10-21 18:53 ` PATAPI via libata promise 20275 (was: RFC: moving drivers to a new drivers/ata directory) Bartlomiej Zolnierkiewicz
2004-10-15 8:37 ` Douglas Gilbert [this message]
2004-10-15 15:00 ` RFC: moving drivers to a new drivers/ata directory Brian King
2004-10-15 17:20 ` Jeff Garzik
2004-10-15 18:32 ` 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=416F8C39.6010804@torque.net \
--to=dougg@torque.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-scsi@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).