All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: dougg@torque.net, SCSI Mailing List <linux-scsi@vger.kernel.org>,
	"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Subject: Re: RFC: moving drivers to a new drivers/ata directory
Date: Fri, 15 Oct 2004 19:32:22 +0100	[thread overview]
Message-ID: <1097865140.10133.184.camel@localhost.localdomain> (raw)
In-Reply-To: <417006F0.5040706@pobox.com>

On Gwe, 2004-10-15 at 18:20, Jeff Garzik wrote:
> Maybe we need a neutral one like 'drivers/storage'.

Where does that leave usb, firewire or i2o 8). At the end of the 
day the only "perfect" division is a single directory "drivers", and
that doesn't work.

Having drivers/ata seems a decent approximation.


      reply	other threads:[~2004-10-15 18:32 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 ` RFC: moving drivers to a new drivers/ata directory Douglas Gilbert
2004-10-15 15:00   ` Brian King
2004-10-15 17:20   ` Jeff Garzik
2004-10-15 18:32     ` Alan Cox [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=1097865140.10133.184.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=dougg@torque.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.