linux-kernel - Re: How to force Kconfig tristate into range n..m?

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: <20070516154459.GA2060@linux.vnet.ibm.com>
Date:	Wed, 16 May 2007 08:44:59 -0700
From:	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
To:	Andi Kleen <ak@...e.de>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: How to force Kconfig tristate into range n..m?

On Wed, May 16, 2007 at 02:18:48PM +0200, Andi Kleen wrote:
> 
> >
> > Is there some other way to prohibit modules from being compiled into
> > the main kernel?
> 
> One way is to use a separate symbol that is not user visible, but depends
> on your main symbol and uses default m
> 
> (similar to the now infamous CONFIG_SCSI_WAIT_SCAN)

Cool!!!  Any problem you see with Randy Dunlap's suggestion of simply
adding "depends on m", though?

						Thanx, Paul
-
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/