Kconfig fails: big select-based circular dependency
broonie at kernel.org
Thu Jun 12 05:18:06 PDT 2014
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.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 819 bytes
Desc: Digital signature
More information about the linux-arm-kernel