From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Andi Kleen <ak@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: How to force Kconfig tristate into range n..m?
Date: Wed, 16 May 2007 08:44:59 -0700 [thread overview]
Message-ID: <20070516154459.GA2060@linux.vnet.ibm.com> (raw)
In-Reply-To: <200705161418.49151.ak@suse.de>
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
prev parent reply other threads:[~2007-05-16 15:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-15 23:30 How to force Kconfig tristate into range n..m? Paul E. McKenney
2007-05-15 23:41 ` 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 [this message]
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=20070516154459.GA2060@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