From: Russell King <rmk@arm.linux.org.uk>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "Adam J. Richter" <adam@yggdrasil.com>,
kaos@ocs.com.au, linux-kernel@vger.kernel.org
Subject: Re: linux-2.4.6-pre6: numerous dep_{bool,tristate} $CONFIG_ARCH_xxx bugs
Date: Sat, 30 Jun 2001 10:20:24 +0100 [thread overview]
Message-ID: <20010630102024.A12009@flint.arm.linux.org.uk> (raw)
In-Reply-To: <200106300435.VAA14173@adam.yggdrasil.com> <E15GF94-0001h6-00@the-village.bc.nu>
In-Reply-To: <E15GF94-0001h6-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Sat, Jun 30, 2001 at 08:26:22AM +0100
On Sat, Jun 30, 2001 at 08:26:22AM +0100, Alan Cox wrote:
> #2
> dep_tristate $FOO $BAR
>
> to say 'FOO requires BAR and must be a similar setting _IF_CONFIGURED_'
Err, how can $BAR be undefined? Configure sets all config variables which
are answered with 'n' to 'n'.
Therefore, if you do:
bool 'PNP?' PNP
dep_tristate 'FOO?' FOO $PNP
and you answer 'n' to PNP, then FOO will be 'n'.
Can you extract an example where #2 is actually used?
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2001-06-30 9:20 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-30 4:35 linux-2.4.6-pre6: numerous dep_{bool,tristate} $CONFIG_ARCH_xxx bugs Adam J. Richter
2001-06-30 7:26 ` Alan Cox
2001-06-30 9:20 ` Russell King [this message]
2001-06-30 11:43 ` Alan Cox
2001-06-30 11:58 ` Russell King
2001-06-30 12:01 ` Alan Cox
2001-06-30 12:02 ` Russell King
2001-06-30 11:45 ` Keith Owens
2001-06-30 12:10 ` Russell King
-- strict thread matches above, loose matches on Subject: below --
2001-06-30 14:57 Adam J. Richter
2001-06-30 15:01 ` Russell King
2001-07-01 2:39 ` Keith Owens
2001-06-30 13:32 Adam J. Richter
2001-06-30 9:38 Adam J. Richter
2001-06-30 4:40 Adam J. Richter
2001-06-30 7:23 ` Alan Cox
2001-06-29 14:10 Adam J. Richter
2001-06-29 14:21 ` Keith Owens
2001-06-29 14:30 ` Russell King
2001-06-29 14:41 ` Keith Owens
2001-06-29 15:19 ` Alan Cox
2001-06-29 14:30 ` Jeff Garzik
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=20010630102024.A12009@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=adam@yggdrasil.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@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