From: Dmitry Torokhov <dtor@insightbb.com>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Fwd: Using select in boolean dependents of a tristate symbol
Date: Wed, 26 Jul 2006 21:05:35 -0400 [thread overview]
Message-ID: <200607262105.36159.dtor@insightbb.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0607270225540.6761@scrub.home>
On Wednesday 26 July 2006 20:42, Roman Zippel wrote:
> Hi,
>
> On Wed, 19 Jul 2006, Dmitry Torokhov wrote:
>
> > Another question for you - what is the best way to describe
> > dependancy of a sub-option on a subsystem so you won't end up with the
> > subsystem as a module and user built in. Something like
> >
> > config IBM_ASM
> > tristate "Device driver for IBM RSA service processor"
> > depends on X86 && PCI && EXPERIMENTAL
> > ...
> > config IBM_ASM_INPUT
> > bool "Support for remote keyboard/mouse"
> > depends on IBM_ASM && (INPUT=y || INPUT=IMB_ASM)
> >
> > But the above feels yucky. Could we have something like:
> >
> > depends on matching(INPUT, IBM_ASM)
>
> This is not really descriptive of what it does, is it?
> Linus suggested a syntax like (IBM_ASM && IMB_ASM<=INPUT)
> Another alternative which works now is to just disable the one invalid
> case explicitely:
>
> depends on IBM_ASM && INPUT
> depends on !(IBM_ASM=y && INPUT=m)
>
OK, then I'll be disabling invalid cases explicitly for now.
Thank you Roman.
--
Dmitry
prev parent reply other threads:[~2006-07-27 1:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <d120d5000607131232i74dfdb9t1a132dfc5dd32bc4@mail.gmail.com>
2006-07-13 19:35 ` Fwd: Using select in boolean dependents of a tristate symbol Dmitry Torokhov
2006-07-13 22:58 ` Roman Zippel
2006-07-14 2:31 ` Dmitry Torokhov
2006-07-14 9:20 ` Roman Zippel
2006-07-19 20:17 ` Dmitry Torokhov
2006-07-19 20:41 ` Valdis.Kletnieks
2006-07-19 20:50 ` Dmitry Torokhov
2006-07-27 0:42 ` Roman Zippel
2006-07-27 1:05 ` Dmitry Torokhov [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=200607262105.36159.dtor@insightbb.com \
--to=dtor@insightbb.com \
--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