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

[Randy Dunlap <randy.dunlap@oracle.com>]

On Tue, 15 May 2007 16:30:02 -0700 Paul E. McKenney wrote:

> Hello!
> 
> It would be nice to constrain RCU_TORTURE_TEST to "n" or "m", excluding
> "y", since "y" gives anti-social results that I have never seen a use
> for.  So I tried adding a "range n m" to the Kconfig.debug entry for
> RCU_TORTURE_TEST.  This gives me the following warning at "make xconfig"
> time:
> 
>    lib/Kconfig.debug:386:warning: range is only allowed for int or hex symbols
> 
> and xconfig ignores the restriction.
> 
> A few clumsy hacks get rid of the error message, but fail to cause
> xconfig to enforce the limit.
> 
> Is there some other way to prohibit modules from being compiled into
> the main kernel?

I think that
	depends on m
will do what you want.  That's what some ancient PCMCIA drivers
do, as well as the crypto test module.


---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/