linux-kernel - Re: tristate and bool not enogh for Kconfig anymore

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

Message-Id: <200710280137.28128.zippel@linux-m68k.org>
Date:	Sun, 28 Oct 2007 01:37:26 +0200
From:	Roman Zippel <zippel@...ux-m68k.org>
To:	Randy Dunlap <rdunlap@...otime.net>
Cc:	Sam Ravnborg <sam@...nborg.org>, Henrik Carlqvist <hc1@...lhem.se>,
	linux-kernel@...r.kernel.org, bunk@...sta.de
Subject: Re: tristate and bool not enogh for Kconfig anymore

Hi,

On Monday 22 October 2007, Randy Dunlap wrote:

> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Another common idiom that we see (and sometimes have problems
> with) is this:
>
> When B (module or subsystem) uses interfaces from A (module or
> subsystem), A can be linked statically into the kernel image or
> can be built as loadable module(s).   This limits how B can be
> built.  If A is linked statically into the kernel image, B can be
> built statically or as loadable module(s).  However, if A is built
> as loadable module(s), then B must be restricted to loadable
> module(s) also.  This can be expressed in kconfig language as:
>
> config B
> 	depends on A = y || A = B

What you describe is a simple "depends on A" and your example won't work 
because it adds a recursive dependency.

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/