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 for Android: free password hash cracker in your pocket

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

Message-Id: <20071020145652.3696de40.rdunlap@xenotime.net>
Date:	Sat, 20 Oct 2007 14:56:52 -0700
From:	Randy Dunlap <rdunlap@...otime.net>
To:	Sam Ravnborg <sam@...nborg.org>
Cc:	Henrik Carlqvist <hc1@...lhem.se>, linux-kernel@...r.kernel.org
Subject: Re: tristate and bool not enogh for Kconfig anymore

On Sat, 20 Oct 2007 21:17:00 +0200 Sam Ravnborg wrote:

> On Sat, Oct 20, 2007 at 02:42:38PM +0200, Henrik Carlqvist wrote:
> > I think there is a need for Kconfig to specify that a functionality could
> > be built as a module or not built at all.
> 
> I assume
> 	depends on MODULES
> 
> should do the trick.

Some modules use (e.g.)
	depends on PCMCIA and m

but using MODULES does make more sense to me.

---
~Randy
-
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/