linux-kernel - Re: Fwd: Using select in boolean dependents of a tristate symbol

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.64.0607270225540.6761@scrub.home>
Date:	Thu, 27 Jul 2006 02:42:20 +0200 (CEST)
From:	Roman Zippel <zippel@...ux-m68k.org>
To:	Dmitry Torokhov <dmitry.torokhov@...il.com>
cc:	linux-kernel@...r.kernel.org
Subject: Re: Fwd: Using select in boolean dependents of a tristate symbol

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)

bye, Roman
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/