[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150923154809.GC18173@wotan.suse.de>
Date: Wed, 23 Sep 2015 17:48:09 +0200
From: "Luis R. Rodriguez" <mcgrof@...e.com>
To: Randy Dunlap <rdunlap@...radead.org>
Cc: "Luis R. Rodriguez" <mcgrof@...not-panic.com>, mmarek@...e.com,
josh@...htriplett.org, jbottomley@...n.com, geert@...ux-m68k.org,
pebolle@...cali.nl, herbert@...dor.apana.org.au, tiwai@...e.de,
yann.morin.1998@...e.fr, corbet@....net,
linux-kbuild@...r.kernel.org, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org, roberto@...osmo.org, zack@...ilon.cc
Subject: Re: [PATCH] kbuild: document recursive dependency limitation /
resolution
On Wed, Jul 29, 2015 at 01:34:50PM -0700, Randy Dunlap wrote:
> On 07/29/15 13:09, Luis R. Rodriguez wrote:
> > +
> > +Kconfig recursive dependency limitations
> > +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> > +
> > +If you've hit the Kconfig error: "recursive dependency detected" you've run
> > +into a recursive dependency issue with Kconfig. Kconfig does not do recursive
> > +dependency resolution, this has a few implications for Kconfig file writers. In
>
> maybe s/,/;/
Fixed.
> > +practice it means that for instance if a driver A selects a few kconfig symbols
> > +another driver B which selects any of these symbols cannot negate any of the
> > +symbols the driver A selected. Because of this current limitation developers
> > +who run into this type of recursive dependency issue have two diverging
> > +options:
> > +
> > + a) Either swap all "select FOO" to "depends on FOO" or,
> > + b) Change the offending "depends on FOO" to "select FOO"
> > +
> > +Kconfig's limitations can be addressed by implementing a SAT solver for it,
> > +but until then, Kconfig is limitted to require developers to use one of
>
> limited
>
I've re-written this section, thanks for the review.
Luis
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists