From: "Randy.Dunlap" <rddunlap@osdl.org>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: what means duplicate "config" entries in Kconfig file?
Date: Wed, 9 Apr 2003 09:08:30 -0700 [thread overview]
Message-ID: <20030409090830.22f58832.rddunlap@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0304090826470.25330-100000@dell>
On Wed, 9 Apr 2003 08:30:34 -0400 (EDT) "Robert P. J. Day" <rpjday@mindspring.com> wrote:
| [i just tried to email the Kconfig maintainer, but sendmail
| suggested that that mail might not have gotten through, so i'll
| toss this out here.]
|
| in my quest to clean up even more kernel config menus,
| i ran across the following oddity in arch/i386/Kconfig:
|
| -----
|
| config MCA
| bool "MCA support"
| depends on !(X86_VISWS || X86_VOYAGER)
| help
| MicroChannel Architecture is found in some IBM PS/2 machines and
| laptops. It is a bus system similar to PCI or ISA. See
| <file:Documentation/mca.txt> (and especially the web page given
| there) before attempting to build an MCA bus kernel.
|
| config MCA
| depends on X86_VOYAGER
| default y if X86_VOYAGER
|
| source "drivers/mca/Kconfig"
|
| -----
|
| i'm not sure what it means to have two config entries with
| identical symbols. can someone clarify this? i'm just confused
| (which should not come as a surprise at this point).
This should be OK. The "depends" clauses are different,
so in the second case, MCA defaults to set/enabled for X86_VOYAGER
(forced, not a user option),
and in the first case, MCA is a user config option.
--
~Randy
next prev parent reply other threads:[~2003-04-09 15:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-09 12:30 Robert P. J. Day
2003-04-09 16:08 ` Randy.Dunlap [this message]
2003-04-09 16:23 ` Roman Zippel
2003-04-09 16:43 ` Robert P. J. Day
2003-04-09 19:54 ` 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=20030409090830.22f58832.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rpjday@mindspring.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
all inboxes | Powered by JetHome®