[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150923155012.GD18173@wotan.suse.de>
Date: Wed, 23 Sep 2015 17:50:12 +0200
From: "Luis R. Rodriguez" <mcgrof@...e.com>
To: Michal Marek <mmarek@...e.com>
Cc: "Luis R. Rodriguez" <mcgrof@...not-panic.com>,
Randy Dunlap <rdunlap@...radead.org>, 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 Tue, Aug 04, 2015 at 01:57:21PM +0200, Michal Marek wrote:
> 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@...e.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.
Great I've expanded a bit on the future required work to feed the curious
so that we don't idle lingering what to do next but rather get folks engaged
and so that they can know where to dive in.
>
> >> +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?
I'll respin a v3 now.
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