From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: linux-kernel@vger.kernel.org, ak@suse.de
Subject: How to force Kconfig tristate into range n..m?
Date: Tue, 15 May 2007 16:30:02 -0700 [thread overview]
Message-ID: <20070515233002.GA9614@linux.vnet.ibm.com> (raw)
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
next reply other threads:[~2007-05-15 23:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-15 23:30 Paul E. McKenney [this message]
2007-05-15 23:41 ` How to force Kconfig tristate into range n..m? Randy Dunlap
2007-05-16 0:18 ` Paul E. McKenney
2007-05-16 12:18 ` Andi Kleen
2007-05-16 14:30 ` Stefan Richter
2007-05-16 15:36 ` Satyam Sharma
2007-05-16 15:44 ` Paul E. McKenney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070515233002.GA9614@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox