[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140612121806.GY5099@sirena.org.uk>
Date: Thu, 12 Jun 2014 13:18:06 +0100
From: Mark Brown <broonie@...nel.org>
To: Geert Uytterhoeven <geert@...ux-m68k.org>
Cc: Russell King - ARM Linux <linux@....linux.org.uk>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Tomasz Figa <tomasz.figa@...il.com>,
Arnd Bergmann <arnd@...db.de>
Subject: Re: Kconfig fails: big select-based circular dependency
On Thu, Jun 12, 2014 at 01:57:03PM +0200, Geert Uytterhoeven wrote:
> Should we have a better separation between select and depends, i.e.
> should kconf plainly reject both being used on the same symbol?
> Is it ever valid to have a symbol that's both selected and used with depends on?
Architecture feature Kconfig symbols typically have the pattern that the
architecture selects ARCH_HAS_FOO and then code that needs the feature
depends on ARCH_HAS_FOO.
Download attachment "signature.asc" of type "application/pgp-signature" (820 bytes)
Powered by blists - more mailing lists