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

Message-Id: <200705161418.49151.ak@suse.de>
Date:	Wed, 16 May 2007 14:18:48 +0200
From:	Andi Kleen <ak@...e.de>
To:	paulmck@...ux.vnet.ibm.com
Cc:	linux-kernel@...r.kernel.org
Subject: Re: How to force Kconfig tristate into range n..m?

>
> 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)

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