From: Adrian Bunk <bunk@fs.tum.de>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6 bug: kconfig implementation doesn't match the spec
Date: Fri, 8 Aug 2003 20:16:13 +0200 [thread overview]
Message-ID: <20030808181612.GC16091@fs.tum.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0308081956250.24676-100000@serv>
On Fri, Aug 08, 2003 at 08:01:20PM +0200, Roman Zippel wrote:
> Hi,
Hi Roman,
> On Fri, 8 Aug 2003, Adrian Bunk wrote:
>
> > > You probably forgot to set MODULES, tristate behaves like bool in this
> > > case and FOO becomes 'y' and '!FOO' is 'n'.
> >
> > No, this is with CONFIG_MODULES=y.
>
> How did you set it? I tried your examples and got the expected and correct
> result.
ups, sorry, you are right. I switched between two trees and these
examples were with CONFIG_MODULES=n. With CONFIG_MODULES=y I observe the
correct results.
> > According to your language definition,
> > m && !m
> > evaluates to "m" (it sounds a bit strange but follows directly from
> > rules (5) and (7) together with the interpretation of "m" as 1 as
> > explained in the section "Menu dependencies" of
> > Documentation/kbuild/kconfig-language.txt).
>
> BTW the reason for (5) !<expr> -> 2-<expr> is that it becomes possible to
> do various transformations with the expressions, e.g. !!<expr> == <expr>.
OTOH, the expression
FOO && !FOO
is not always "n" as you might expect.
> bye, Roman
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
prev parent reply other threads:[~2003-08-08 18:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-08 14:51 Adrian Bunk
2003-08-08 15:16 ` Roman Zippel
2003-08-08 17:47 ` Adrian Bunk
2003-08-08 18:01 ` Roman Zippel
2003-08-08 18:16 ` Adrian Bunk [this message]
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=20030808181612.GC16091@fs.tum.de \
--to=bunk@fs.tum.de \
--cc=linux-kernel@vger.kernel.org \
--cc=zippel@linux-m68k.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
all inboxes | Powered by JetHome®