public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Roman Zippel <zippel@linux-m68k.org>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Sam Ravnborg <sam@ravnborg.org>,
	Henrik Carlqvist <hc1@poolhem.se>,
	linux-kernel@vger.kernel.org, bunk@stusta.de
Subject: Re: tristate and bool not enogh for Kconfig anymore
Date: Sun, 28 Oct 2007 01:37:26 +0200	[thread overview]
Message-ID: <200710280137.28128.zippel@linux-m68k.org> (raw)
In-Reply-To: <20071021201416.4ccde183.rdunlap@xenotime.net>

Hi,

On Monday 22 October 2007, Randy Dunlap wrote:

> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Another common idiom that we see (and sometimes have problems
> with) is this:
>
> When B (module or subsystem) uses interfaces from A (module or
> subsystem), A can be linked statically into the kernel image or
> can be built as loadable module(s).   This limits how B can be
> built.  If A is linked statically into the kernel image, B can be
> built statically or as loadable module(s).  However, if A is built
> as loadable module(s), then B must be restricted to loadable
> module(s) also.  This can be expressed in kconfig language as:
>
> config B
> 	depends on A = y || A = B

What you describe is a simple "depends on A" and your example won't work 
because it adds a recursive dependency.

bye, Roman

  parent reply	other threads:[~2007-10-27 23:37 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
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 [this message]
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=200710280137.28128.zippel@linux-m68k.org \
    --to=zippel@linux-m68k.org \
    --cc=bunk@stusta.de \
    --cc=hc1@poolhem.se \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    --cc=sam@ravnborg.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