From: Jens Axboe <axboe@suse.de>
To: Christoph Hellwig <hch@infradead.org>,
"Randy.Dunlap" <rdunlap@xenotime.net>,
lkml <linux-kernel@vger.kernel.org>, jgarzik <jgarzik@pobox.com>,
jejb <james.bottomley@steeleye.com>
Subject: Re: [PATCH/RFC] SATA in its own config menu
Date: Mon, 16 Jan 2006 15:12:03 +0100 [thread overview]
Message-ID: <20060116141203.GD3945@suse.de> (raw)
In-Reply-To: <20060116121328.GA12871@infradead.org>
On Mon, Jan 16 2006, Christoph Hellwig wrote:
> On Sun, Jan 15, 2006 at 01:57:28PM -0800, Randy.Dunlap wrote:
> > From: Randy Dunlap <rdunlap@xenotime.net>
> >
> > Put SATA into its own menu. Reason: using SCSI is an
> > implementation detail that users need not know about.
> >
> > Enabling SATA selects SCSI since SATA uses SCSI as a function
> > library supplier. It also enables BLK_DEV_SD since that is
> > what SATA drives look like in Linux.
>
> we'll soon support (or already do?) support sata atapi, when this
> won't be true anymore. Please never select scsi upper drivers from
> lower drivers, this independence is the whole point of the layered
> architecture.
It's already possible, and besides you could be using sg with your SATA
devices stand-alone if you so wanted. So this selection is indeed a
nonsensical one, it's an invalid dependency.
--
Jens Axboe
next prev parent reply other threads:[~2006-01-16 14:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-15 21:57 [PATCH/RFC] SATA in its own config menu Randy.Dunlap
2006-01-16 12:08 ` Jan Engelhardt
2006-01-16 12:13 ` Christoph Hellwig
2006-01-16 14:12 ` Jens Axboe [this message]
2006-01-17 16:50 ` Jan Engelhardt
2006-01-17 16:51 ` Christoph Hellwig
2006-01-16 14:16 ` Jeff Garzik
2006-01-17 4:59 ` Randy.Dunlap
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=20060116141203.GD3945@suse.de \
--to=axboe@suse.de \
--cc=hch@infradead.org \
--cc=james.bottomley@steeleye.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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).