From: "Luis R. Rodriguez" <mcgrof@suse.com>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>,
mmarek@suse.com, josh@joshtriplett.org, jbottomley@odin.com,
geert@linux-m68k.org, herbert@gondor.apana.org.au, tiwai@suse.de,
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:53:13 +0200 [thread overview]
Message-ID: <20150923155313.GE18173@wotan.suse.de> (raw)
In-Reply-To: <1441281409.2439.96.camel@tiscali.nl>
On Thu, Sep 03, 2015 at 01:56:49PM +0200, Paul Bolle wrote:
> Hi Luis,
>
> (This landed in my Inbox when I was away from keyboard for a few weeks.
> And then I dragged my feet a bit in answering this. Sorry about that.)
No worries I will note that I try to be as thorough so sadly this can go on
forever... I've taken your feedback and placed it first to explain *why* this
happens, then I added another subsection explaining one practical ramification
of such issue. Lastly I've exanded the patch with some homework for folks to
consider.
Luis
next prev parent reply other threads:[~2015-09-23 15:53 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
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 [this message]
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=20150923155313.GE18173@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=roberto@dicosmo.org \
--cc=tiwai@suse.de \
--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