linux-kernel - Re: your old menuconfig patch series, and select

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <alpine.LNX.1.10.0803240542030.27005@fbirervta.pbzchgretzou.qr>
Date:	Mon, 24 Mar 2008 05:47:28 +0100 (CET)
From:	Jan Engelhardt <jengelh@...putergmbh.de>
To:	Henrique de Moraes Holschuh <hmh@....eng.br>
cc:	linux-kernel@...r.kernel.org
Subject: Re: your old menuconfig patch series, and select


On Monday 2008-03-24 05:05, Henrique de Moraes Holschuh wrote:
>
> In your menuconfig patch series to convert menu into menuconfig,
> you used "if <new menuconfig symbol" quite often.
>
> That causes serious issues with "select".  E.g. currently "select
> LEDS_CLASS" does not work, because it is inside a "if NEW_LEDS".
>[...]
> What's the best solution for this?  Drop the "if <menuconfig symbol>"
> and add lots of "depends on <menuconfig symbol>"?  Or hunt down every
> symbol selected inside an if and add the required select for the
> menuconfig symbol?

It "does not work" either if LEDS_CLASS is put outside of the if block
and instead gets a "depends on LEDS_CLASS".

So I am not sure what the problem you perceive really is, other than
"enabling A selecting B depending on (turned off) C"-is-allowed. :)
--
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/