From: James Bottomley <James.Bottomley@steeleye.com>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: kieran@ihateaol.co.uk,
Linux Kernel <linux-kernel@vger.kernel.org>,
SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: Why is CONFIG_SCSI_QLA2X_X always enabled?
Date: 22 Apr 2004 14:56:01 -0400 [thread overview]
Message-ID: <1082660161.1778.100.camel@mulgrave> (raw)
In-Reply-To: <20040422113750.3ad2a065.rddunlap@osdl.org>
On Thu, 2004-04-22 at 14:37, Randy.Dunlap wrote:
> which isn't a problem by itself, as you suggest (maybe?).
Yes, it was a harmless evolutionary addition to save having a depends
SCSI && PCI on every config option in the qla2xxx/Kconfig.
However, I believe in the Kconfig language there is a way of only
sourcing the qla2xxx/Kconfig if SCSI && PCI or of making it a menu
dependent on SCSI && PCI, so the variable could be eliminated nicely
that way.
James
next prev parent reply other threads:[~2004-04-22 18:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-22 15:48 Why is CONFIG_SCSI_QLA2X_X always enabled? 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
2004-04-22 18:56 ` James Bottomley [this message]
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=1082660161.1778.100.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=kieran@ihateaol.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=rddunlap@osdl.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