From: Roman Zippel <zippel@linux-m68k.org>
To: Adrian Bunk <bunk@fs.tum.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Surprising Kconfig depends semantics
Date: Fri, 8 Aug 2003 17:13:48 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.44.0308081708390.714-100000@serv> (raw)
In-Reply-To: <20030808144408.GX16091@fs.tum.de>
Hi,
On Fri, 8 Aug 2003, Adrian Bunk wrote:
> CONFIG_SERIO=m with CONFIG_KEYBOARD_ATKBD=y shouldn't be a valid
> combination.
>
> The correct solution is most likely a
> default y if INPUT=y && INPUT_KEYBOARD=y && SERIO=y
> default m if INPUT!=n && INPUT_KEYBOARD!=n && SERIO!=n
This is probably the easiest solution:
default INPUT_KEYBOARD && SERIO
(INPUT_KEYBOARD already depends on INPUT)
> The semantics that in
>
> config FOO
> tristate
> default y if BAR
>
> FOO will be set to y if BAR=m is a bit surprising.
Why?
bye, Roman
next prev parent reply other threads:[~2003-08-08 15:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-08 14:44 Adrian Bunk
2003-08-08 15:13 ` Roman Zippel [this message]
2003-08-08 16:26 ` James Simmons
2003-08-08 18:30 ` Adrian Bunk
2003-08-08 18:58 ` Roman Zippel
2003-08-08 22:45 ` James Simmons
2003-08-08 23:26 ` 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=Pine.LNX.4.44.0308081708390.714-100000@serv \
--to=zippel@linux-m68k.org \
--cc=bunk@fs.tum.de \
--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
all inboxes | Powered by JetHome®