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-next>] [day] [month] [year] [list]

Message-ID: <d120d5000607191317k2e773af3ta5034a37db5ad97d@mail.gmail.com>
Date:	Wed, 19 Jul 2006 16:17:38 -0400
From:	"Dmitry Torokhov" <dmitry.torokhov@...il.com>
To:	"Roman Zippel" <zippel@...ux-m68k.org>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Fwd: Using select in boolean dependents of a tristate symbol

On 7/14/06, Roman Zippel <zippel@...ux-m68k.org> wrote:
>
> What you could do is to use "select INPUT_FF_MEMLESS if HID" to make it
> visible that this dependency is actually for select.
> This point is a little subtle and I'm not completely happy with it, maybe
> I'm going to split this into two select variations - one which includes
> all the dependencies and one which only uses the config symbol to select.
>

Roman,

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)

Thank you.

-- 
Dmitry
-
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/