From: "Randy.Dunlap" <rddunlap@osdl.org>
To: jejb <james.bottomley@steeleye.com>
Cc: kieran@ihateaol.co.uk, linux-kernel@vger.kernel.org,
linux-scsi@vger.kernel.org
Subject: Re: Why is CONFIG_SCSI_QLA2X_X always enabled?
Date: Thu, 22 Apr 2004 11:37:50 -0700 [thread overview]
Message-ID: <20040422113750.3ad2a065.rddunlap@osdl.org> (raw)
In-Reply-To: <20040422111552.5e14de00.rddunlap@osdl.org>
On Thu, 22 Apr 2004 11:15:52 -0700 Randy.Dunlap wrote:
| On 22 Apr 2004 13:28:46 -0400 James Bottomley wrote:
|
| | On Thu, 2004-04-22 at 13:12, Randy.Dunlap wrote:
| | > As it is, for some large %age of users (say 99% ?), those 6 qla drivers
| | > show up in the config menu when they aren't needed or wanted.
| | > They get in the way.
| |
| | So you want a "Do you want Qlogic drivers" question followed by the 6
| | drivers if Y?
| |
| | I'm less enthused about that. I know there's precedent for it in the
| | net drivers, but I've always thought it caused more confusion than it
| | removed. Traditionally, in SCSI, we've always presented every possible
| | driver in our list.
BTW, thanks for clarifying that. Now we (or I) know.
| | I thought the initial complaint you were trying to fix was the "why does
| | this show up in my .config one"?
|
| The initial complaint was in $SUBJECT:
| .config file always contains CONFIG_SCSI_QLA2XXX=y
which isn't a problem by itself, as you suggest (maybe?).
| and that's not needed, but the Kconfig file as is causes that.
| Then that causes the further noise.
--
~Randy
next prev parent reply other threads:[~2004-04-22 18:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-22 15:48 Kieran
2004-04-22 16:28 ` Randy.Dunlap
2004-04-22 16:39 ` James Bottomley
2004-04-22 17:12 ` Randy.Dunlap
2004-04-22 17:28 ` James Bottomley
2004-04-22 18:15 ` Randy.Dunlap
2004-04-22 18:37 ` Randy.Dunlap [this message]
2004-04-22 18:56 ` James Bottomley
2004-04-22 19:28 ` Roman Zippel
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=20040422113750.3ad2a065.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=james.bottomley@steeleye.com \
--cc=kieran@ihateaol.co.uk \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®