From: Ralf Baechle <ralf@linux-mips.org>
To: Markos Chandras <markos.chandras@imgtec.com>
Cc: linux-mips@linux-mips.org, Michal Marek <mmarek@suse.cz>,
linux-kbuild@vger.kernel.org
Subject: Re: [PATCH] MIPS: Kconfig: Set default value for the "Kernel code model"
Date: Wed, 12 Jun 2013 13:20:09 +0200 [thread overview]
Message-ID: <20130612112009.GA7422@linux-mips.org> (raw)
In-Reply-To: <20130611154129.GD13126@linux-mips.org>
Here's a simplified test case:
< --------- bite here --------- >
choice
prompt "choice 1"
config FOO1
bool "foo 1"
config FOO2
bool "foo 2"
endchoice
choice
prompt "frob"
config BAR
bool "bar"
depends on FOO2
endchoice
< --------- bite here --------- >
Save this to a file, then run:
scripts/kconfig/conf --randconfig /tmp/xxx && cat .config
There will be two possible variants for generated .config files:
< --------- Variant 1 --------- >
CONFIG_FOO1=y
# CONFIG_FOO2 is not set
< --------- Variant 2 --------- >
# CONFIG_FOO1 is not set
# CONFIG_FOO2 is not set
< --------- End --------- >
The intended third outcome which would be
< --------- doesn't happen ---- >
# CONFIG_FOO1 is not set
CONFIG_FOO2=y
< --------- End --------------- >
never gets generated.
Pretty much any tempering with this test case will change the behaviour.
For example removing the "depends on FOO2" line will result in the
behaviour of either CONFIG_FOO1 or CONFIG_FOO2 being set to y but never
none or both. Other minor changes might result in both symbols getting
set.
Ralf
next prev parent reply other threads:[~2013-06-12 11:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1370944336-13703-1-git-send-email-markos.chandras@imgtec.com>
2013-06-11 15:41 ` [PATCH] MIPS: Kconfig: Set default value for the "Kernel code model" Ralf Baechle
2013-06-12 11:20 ` Ralf Baechle [this message]
2013-06-12 11:50 ` Markos Chandras
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=20130612112009.GA7422@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=markos.chandras@imgtec.com \
--cc=mmarek@suse.cz \
/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