From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Folkert van Heusden <folkert@vanheusden.com>,
linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: sata & scsi suggestion for make menuconfig
Date: Sat, 08 Sep 2007 21:45:49 +0200 [thread overview]
Message-ID: <46E2FBED.2050705@s5r6.in-berlin.de> (raw)
In-Reply-To: <20070908094852.3a6fd3f0.randy.dunlap@oracle.com>
Randy Dunlap wrote:
> On Sat, 08 Sep 2007 18:44:46 +0200 Stefan Richter wrote:
>> Randy Dunlap wrote:
>>> The problem with 'select' here is that it will enable BLK_DEV_SD,
>>> but if SCSI is not enabled, it will not become enabled -- i.e.,
>>> select does not follow the dependency chain. So usually the
>>> kernel will not build unless SCSI is enabled by the user.
...
>> I checked the dependencies. ATA depends on SCSI (actually, selects
>> SCSI), so all is well. Otherwise I would have added more dependencies
>> to ATA_SD.
>
> Ah, that's good, then.
Not completely though. Whenever a 'select' is inserted into the
dependency graph, the whole thing becomes more fragile WRT future changes.
--
Stefan Richter
-=====-=-=== =--= -=---
http://arcgraph.de/sr/
prev parent reply other threads:[~2007-09-08 19:47 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
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 [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=46E2FBED.2050705@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=folkert@vanheusden.com \
--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