From: "Luis R. Rodriguez" <mcgrof@suse.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>,
mmarek@suse.com, josh@joshtriplett.org, jbottomley@odin.com,
geert@linux-m68k.org, pebolle@tiscali.nl,
herbert@gondor.apana.org.au, tiwai@suse.de,
yann.morin.1998@free.fr, corbet@lwn.net,
linux-kbuild@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, roberto@dicosmo.org,
zack@upsilon.cc
Subject: Re: [PATCH] kbuild: document recursive dependency limitation / resolution
Date: Wed, 23 Sep 2015 17:48:09 +0200 [thread overview]
Message-ID: <20150923154809.GC18173@wotan.suse.de> (raw)
In-Reply-To: <55B938EA.2080402@infradead.org>
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
next prev parent reply other threads:[~2015-09-23 15:48 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-29 20:09 [PATCH] kbuild: document recursive dependency limitation / resolution Luis R. Rodriguez
2015-07-29 20:34 ` Randy Dunlap
2015-08-04 11:57 ` Michal Marek
2015-08-04 12:05 ` Paul Bolle
2015-09-23 15:50 ` Luis R. Rodriguez
2015-09-23 15:48 ` Luis R. Rodriguez [this message]
2015-07-29 20:54 ` josh
2015-09-23 15:46 ` Luis R. Rodriguez
2015-08-05 11:57 ` Paul Bolle
2015-08-10 18:57 ` Luis R. Rodriguez
2015-09-03 11:56 ` Paul Bolle
2015-09-08 13:12 ` Luis R. Rodriguez
2015-09-23 15:53 ` Luis R. Rodriguez
2015-09-23 16:41 ` [PATCH v3] " Luis R. Rodriguez
2015-10-04 13:42 ` Valentin Rothberg
2015-10-05 23:03 ` Luis R. Rodriguez
2015-10-06 8:19 ` Valentin Rothberg
2015-10-06 8:32 ` Paul Bolle
2015-10-06 9:22 ` Valentin Rothberg
2015-10-07 23:08 ` Luis R. Rodriguez
2015-10-06 9:16 ` Paul Bolle
2015-10-07 23:16 ` [PATCH v4] " Luis R. Rodriguez
2015-10-08 13:37 ` Michal Marek
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=20150923154809.GC18173@wotan.suse.de \
--to=mcgrof@suse.com \
--cc=corbet@lwn.net \
--cc=geert@linux-m68k.org \
--cc=herbert@gondor.apana.org.au \
--cc=jbottomley@odin.com \
--cc=josh@joshtriplett.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@do-not-panic.com \
--cc=mmarek@suse.com \
--cc=pebolle@tiscali.nl \
--cc=rdunlap@infradead.org \
--cc=roberto@dicosmo.org \
--cc=tiwai@suse.de \
--cc=yann.morin.1998@free.fr \
--cc=zack@upsilon.cc \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.