From: Roman Zippel <zippel@linux-m68k.org>
To: Randy Dunlap <rdunlap@xenotime.net>
Subject: Re: tristate and bool not enogh for Kconfig anymore
Date: Sun, 28 Oct 2007 01:37:26 +0200
User-Agent: KMail/1.9.7
Cc: Sam Ravnborg <sam@ravnborg.org>, Henrik Carlqvist <hc1@poolhem.se>,
       linux-kernel@vger.kernel.org, bunk@stusta.de
References: <200710201257.55616.nick@ukfsn.org> <20071021174748.92abc989.rdunlap@xenotime.net> <20071021201416.4ccde183.rdunlap@xenotime.net>
In-Reply-To: <20071021201416.4ccde183.rdunlap@xenotime.net>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200710280137.28128.zippel@linux-m68k.org>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1078
Lines: 28

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/