From: "Randy.Dunlap" <rddunlap@osdl.org>
To: James Bottomley <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 10:12:06 -0700 [thread overview]
Message-ID: <20040422101206.70133b42.rddunlap@osdl.org> (raw)
In-Reply-To: <1082651974.1778.52.camel@mulgrave>
On 22 Apr 2004 12:39:34 -0400 James Bottomley wrote:
| On Thu, 2004-04-22 at 12:28, Randy.Dunlap wrote:
| > A nuisance or annoyance perhaps. Here's a patch for it.
|
| No, it's a variable used to determine whether the user should be asked
| about qla2xxx or not.
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.
| The proposed patch is obviously not correct, because we don't want the
| user to be asked about it.
You want it to always be presented (if PCI && SCSI) ?
No, it should be a selectable option iff PCI && SCSI.
| A better fix might be to make the qla2xxx a menu dependent on SCSI &&
| PCI
It already does. The problem is that is defaults to the value of
(SCSI && PCI) when a large number of people don't need that
default value. IOW, it's a bad choice for a default value.
--
~Randy
"We have met the enemy and he is us." -- Pogo (by Walt Kelly)
next prev parent reply other threads:[~2004-04-22 17:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4087E95F.5050409@ihateaol.co.uk>
2004-04-22 16:28 ` Why is CONFIG_SCSI_QLA2X_X always enabled? Randy.Dunlap
2004-04-22 16:39 ` James Bottomley
2004-04-22 17:12 ` Randy.Dunlap [this message]
2004-04-22 17:28 ` James Bottomley
2004-04-22 18:15 ` Randy.Dunlap
2004-04-22 18:37 ` Randy.Dunlap
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=20040422101206.70133b42.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