From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: Folkert van Heusden <folkert@vanheusden.com>,
Randy Dunlap <randy.dunlap@oracle.com>,
linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: sata & scsi suggestion for make menuconfig
Date: Sat, 08 Sep 2007 09:56:08 +0200 [thread overview]
Message-ID: <46E25598.3060305@s5r6.in-berlin.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0709080927490.25942@fbirervta.pbzchgretzou.qr>
Jan Engelhardt wrote:
> On Sep 8 2007 09:05, Stefan Richter wrote:
>> config ATA_SD
>> tristate "SATA/PATA HDD support (via SCSI disk support)"
>> depends on ATA
>> select BLK_DEV_SD
>> help
>> 'SCSI disk support' is required to access SATA HDDs. It is
[...]
>> You can say Y or M here to select SCSI disk support, or you
>> can do so in the 'SCSI device support' section.
[...]
> And what uses ATA_SD, or is the user supposed to manually enable it?
It is merely there to produce the prompt which people asked for.
CONFIG_ATA_SD (or CONFIG_ATA_BLK_DEV_SD or whatever) won't turn up in
any Makefile or source code.
Note, I'm not fond of 'select' nor of dummy Kconfig variables. Plus I
can personally live very well with the current solution (sd_mod et al
are mentioned in the help text at CONFIG_ATA). That's why I posted only
the example instead of a complete patch.
--
Stefan Richter
-=====-=-=== =--= -=---
http://arcgraph.de/sr/
next prev parent reply other threads:[~2007-09-08 7:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070907124800.GP16806@vanheusden.com>
[not found] ` <20070907083522.3191a4ba.randy.dunlap@oracle.com>
[not found] ` <20070907155903.GR16806@vanheusden.com>
[not found] ` <46E17A81.7020304@s5r6.in-berlin.de>
[not found] ` <20070907230529.GX16806@vanheusden.com>
2007-09-08 7:05 ` sata & scsi suggestion for make menuconfig Stefan Richter
2007-09-08 7:29 ` Jan Engelhardt
2007-09-08 7:56 ` Stefan Richter [this message]
2007-09-08 16:31 ` Randy Dunlap
2007-09-08 16:44 ` Stefan Richter
2007-09-08 16:48 ` Randy Dunlap
2007-09-08 19:45 ` Stefan Richter
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=46E25598.3060305@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=folkert@vanheusden.com \
--cc=jengelh@computergmbh.de \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
/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