From: Sam Ravnborg <sam@ravnborg.org>
To: Adrian Bunk <bunk@kernel.org>
Cc: Randy Dunlap <randy.dunlap@oracle.com>, linux-kbuild@vger.kernel.org
Subject: Re: [2.6 patch] kconfig-language.txt: remove bogus hint
Date: Sun, 4 May 2008 08:17:41 +0200 [thread overview]
Message-ID: <20080504061741.GA14784@uranus.ravnborg.org> (raw)
In-Reply-To: <20080503231535.GY5838@cs181133002.pp.htv.fi>
On Sun, May 04, 2008 at 02:15:35AM +0300, Adrian Bunk wrote:
> This kconfig construct described here is required in a different and
> much more complicated situation.
Please elaborate...
Sam
>
> For the use case the hint claimed it would be a simple dependency is
> enough.
>
> Signed-off-by: Adrian Bunk <bunk@kernel.org>
>
> ---
> 8e3fd4a5e77c9cd1b52989cd72e984b47ad426b4 diff --git a/Documentation/kbuild/kconfig-language.txt b/Documentation/kbuild/kconfig-language.txt
> index 00b950d..c412c24 100644
> --- a/Documentation/kbuild/kconfig-language.txt
> +++ b/Documentation/kbuild/kconfig-language.txt
> @@ -377,27 +377,3 @@ config FOO
>
> limits FOO to module (=m) or disabled (=n).
>
> -
> -Build limited by a third config symbol which may be =y or =m
> -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> -A common idiom that we see (and sometimes have problems with) is this:
> -
> -When option C in B (module or subsystem) uses interfaces from A (module
> -or subsystem), and both A and B are tristate (could be =y or =m if they
> -were independent of each other, but they aren't), then we need to limit
> -C such that it cannot be built statically if A is built as a loadable
> -module. (C already depends on B, so there is no dependency issue to
> -take care of here.)
> -
> -If A is linked statically into the kernel image, C can be built
> -statically or as loadable module(s). However, if A is built as loadable
> -module(s), then C must be restricted to loadable module(s) also. This
> -can be expressed in kconfig language as:
> -
> -config C
> - depends on A = y || A = B
> -
> -or for real examples, use this command in a kernel tree:
> -
> -$ find . -name Kconfig\* | xargs grep -ns "depends on.*=.*||.*=" | grep -v orig
> -
>
next prev parent reply other threads:[~2008-05-04 6:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-03 23:15 [2.6 patch] kconfig-language.txt: remove bogus hint Adrian Bunk
2008-05-04 6:17 ` Sam Ravnborg [this message]
2008-05-04 8:01 ` Adrian Bunk
2008-05-04 11:27 ` Sam Ravnborg
2008-05-04 12:10 ` Adrian Bunk
2008-05-04 12:26 ` Sam Ravnborg
2008-05-04 17:25 ` Randy Dunlap
2008-05-04 17:51 ` Adrian Bunk
2008-05-04 17:55 ` Randy Dunlap
2008-05-04 19:08 ` Sam Ravnborg
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=20080504061741.GA14784@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=bunk@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
/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