From: Sam Ravnborg <sam@ravnborg.org>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Henrik Carlqvist <hc1@poolhem.se>, linux-kernel@vger.kernel.org
Subject: Re: tristate and bool not enogh for Kconfig anymore
Date: Sun, 21 Oct 2007 23:03:13 +0200 [thread overview]
Message-ID: <20071021210313.GA6725@uranus.ravnborg.org> (raw)
In-Reply-To: <20071021094517.78dd1916.rdunlap@xenotime.net>
On Sun, Oct 21, 2007 at 09:45:17AM -0700, Randy Dunlap wrote:
> > Is there any other way to specify that a functionality can only be built
> > as a module, not built into the kernel?
>
> config FOO
> depends on BAR && m
>
> restricts FOO to module-only.
>
> > In my firsta attempts to post about these tests my post ended up not on
> > the mailing list but as a reply to Sam Ravnborg only, apologies for
> > that...
This is obviously the right solution.
Randy - we should document this somewhere together with more kconfig tips'n'tricks.
A new document or do we extend kconfig-language?
Sam
next prev parent reply other threads:[~2007-10-21 21:01 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-20 11:57 [PATCH] Kconfig bug Nick Warne
2007-10-20 12:42 ` tristate and bool not enogh for Kconfig anymore Henrik Carlqvist
2007-10-20 19:17 ` Sam Ravnborg
2007-10-20 21:56 ` Randy Dunlap
2007-10-21 4:47 ` Valdis.Kletnieks
2007-10-21 10:24 ` Henrik Carlqvist
2007-10-21 16:45 ` Randy Dunlap
2007-10-21 20:42 ` Henrik Carlqvist
2007-10-21 21:03 ` Sam Ravnborg [this message]
2007-10-22 0:47 ` Randy Dunlap
2007-10-22 3:14 ` Randy Dunlap
2007-10-22 4:42 ` Randy Dunlap
2007-10-27 23:37 ` Roman Zippel
2007-10-22 10:11 ` Christoph Hellwig
2007-10-22 10:32 ` Alexander E. Patrakov
2007-10-22 10:57 ` Christoph Hellwig
2007-10-22 11:27 ` Alexander E. Patrakov
2007-10-22 12:53 ` Christoph Hellwig
2007-10-22 13:18 ` Alexander E. Patrakov
2007-10-22 11:46 ` Helge Hafting
2007-10-22 21:50 ` Henrik Carlqvist
2007-10-27 12:26 ` [PATCH] Kconfig bug Nick Warne
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=20071021210313.GA6725@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=hc1@poolhem.se \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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