From: Michal Marek <mmarek@suse.com>
To: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
Cc: Randy Dunlap <rdunlap@infradead.org>,
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, "Luis R. Rodriguez" <mcgrof@suse.com>
Subject: Re: [PATCH] kbuild: document recursive dependency limitation / resolution
Date: Tue, 4 Aug 2015 13:57:21 +0200 [thread overview]
Message-ID: <55C0A8A1.2030706@suse.com> (raw)
In-Reply-To: <55B938EA.2080402@infradead.org>
Dne 29.7.2015 v 22:34 Randy Dunlap napsal(a):
> On 07/29/15 13:09, Luis R. Rodriguez wrote:
>> From: "Luis R. Rodriguez" <mcgrof@suse.com>
>>
>> Recursive dependency issues with kconfig are unavoidable due to
>> some limitations with kconfig, since these issues are recurring
>> provide a hint to the user how they can resolve these dependency
>> issues and also document why such limitation exists.
Good idea.
>> +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
should I apply the patch with the typo fixed or are you going to send a v2?
Thanks,
Michal
next prev parent reply other threads:[~2015-08-04 11:57 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 [this message]
2015-08-04 12:05 ` Paul Bolle
2015-09-23 15:50 ` Luis R. Rodriguez
2015-09-23 15:48 ` Luis R. Rodriguez
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=55C0A8A1.2030706@suse.com \
--to=mmarek@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=mcgrof@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox