From: Christoph Hellwig <hch@infradead.org>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Christoph Hellwig <hch@infradead.org>,
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: Wed, 20 Oct 2004 16:34:44 +0100 [thread overview]
Message-ID: <20041020153444.GA21881@infradead.org> (raw)
In-Reply-To: <41700747.6040506@pobox.com>
On Fri, Oct 15, 2004 at 01:22:15PM -0400, Jeff Garzik wrote:
> Welcome to the real world, where SCSI drivers can be for non-SCSI
> hardware, and where SCSI hardware can also drive non-SCSI devices.
>
> Fix your subsystem, if it can't support SCSI drivers outside of
> drivers/scsi.
It's not about not working but making life for the scsi maintainers easier.
next prev parent reply other threads:[~2004-10-20 15:34 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 [this message]
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
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=20041020153444.GA21881@infradead.org \
--to=hch@infradead.org \
--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 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.