How to force Kconfig tristate into range n..m?
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?
Thanx, Paul
Quoted 10 lines · On Tue, 15 May 2007 16:30:02 -0700 Paul E. McKenney wrote:
Hello!
It would be nice to constrain
RCU_TORTURE_TESTto "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 theKconfig.debugentry forRCU_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
Quoted 7 lines
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 ***
Quoted 17 lines · Randy Dunlap
Quoted 15 lines · On Tue, 15 May 2007 16:30:02 -0700 Paul E. McKenney wrote:
Hello!
It would be nice to constrain
RCU_TORTURE_TESTto "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 theKconfig.debugentry forRCU_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.
Quoted 7 lines
Quoted 2 lines
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.
This indeed works! Thank you!!!
Thanx, Paul
Quoted 4 lines
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
Quoted 4 lines · Andi Kleen
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)
Actually CONFIG_SCSI_WAIT_SCAN should be visible and restricted to m or n. :-)
Signature · 3 lines
Stefan Richter -=====-=-=== -=-= =---- http://arcgraph.de/sr/
Quoted 2 lines · Stefan Richter
Quoted 1 line · Andi Kleen
One way is to use a separate symbol that is not user visible,
Gargle ... gargle ...
Quoted 2 lines
Quoted 2 lines
but depends on your main symbol
and uses default m
Aargh!
Please don't recommend such a hack.
[ Note to LKML archive readers: Andi never said this, you never read this. ]
Quoted 4 lines
Quoted 1 line
(similar to the now infamous
CONFIG_SCSI_WAIT_SCAN)Actually
CONFIG_SCSI_WAIT_SCANshould be visible and restricted to m or n. :-)
Actually, SCSI_WAIT_SCAN doesn't want to be a separate module in the first place :-)
Quoted 9 lines · Andi Kleen
Quoted 4 lines
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