From: Michal Marek <mmarek@suse.cz>
To: Mark Salter <msalter@redhat.com>, Stephen Warren <swarren@nvidia.com>
Cc: Jon Loeliger <jdl@jdl.com>,
David Gibson <david@gibson.dropbear.id.au>,
Russell King <linux@arm.linux.org.uk>,
Aurelien Jacquiot <a-jacquiot@ti.com>,
Michal Simek <monstr@monstr.eu>, Jonas Bonn <jonas@southpole.se>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
Grant Likely <grant.likely@secretlab.ca>,
Rob Herring <rob.herring@calxeda.com>,
Arnd Bergmann <arnd@arndb.de>,
linux-kbuild@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-c6x-dev@linux-c6x.org,
microblaze-uclinux@itee.uq.edu.au, linux@openrisc.net,
linuxppc-dev@lists.ozlabs.org,
Devicetree Discuss <devicetree-discuss@lists.ozlabs.org>
Subject: Re: [PATCH 2/2] Kbuild: Use dtc's -d (dependency) option
Date: Sat, 14 Jan 2012 23:51:29 +0100 [thread overview]
Message-ID: <4F1206F1.5090405@suse.cz> (raw)
In-Reply-To: <1326310587.2535.291.camel@deneb.redhat.com>
On 11.1.2012 20:36, Mark Salter wrote:
> On Mon, 2012-01-09 at 11:38 -0700, Stephen Warren wrote:
>> This hooks dtc into Kbuild's dependency system.
>>
>> Thus, for example, "make dtbs" will rebuild tegra-harmony.dtb if only
>> tegra20.dtsi has changed yet tegra-harmony.dts has not. The previous
>> lack of this feature recently caused me to have very confusing "git
>> bisect" results.
>>
>> For ARM, it's obvious what to add to $(targets). I'm not familiar enough
>> with other architectures to know what to add there. Powerpc appears to
>> already add various .dtb files into $(targets), but the other archs may
>> need something added to $(targets) to work.
>>
>> Signed-off-by: Stephen Warren <swarren@nvidia.com>
>>
>
> Acked-by: Mark Salter <msalter@redhat.com>
>
> For the arch/c6x bit.
As the C6X port has been merged in this merge window, I can't easily
apply this patch to my kbuild branch and at the same time please Linus
by basing the pull request on a tagged release. So I'm going to drop the
arch/c6x part to keep the kbuild branch "pretty" and let either Mark or
Stephen send the patch to Linus directly, once he has merged the kbuild
branch. Would that work?
Thanks,
Michal
next prev parent reply other threads:[~2012-01-14 22:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-09 18:38 [PATCH 1/2] dtc: Implement -d option to write out a dependency file Stephen Warren
2012-01-09 18:38 ` [PATCH 2/2] Kbuild: Use dtc's -d (dependency) option Stephen Warren
2012-01-10 3:12 ` Shawn Guo
2012-01-11 19:36 ` Mark Salter
2012-01-14 22:51 ` Michal Marek [this message]
2012-01-17 17:20 ` Stephen Warren
2012-01-17 18:26 ` Mark Salter
2012-01-18 10:07 ` Michal Marek
2012-01-09 18:58 ` [PATCH 1/2] dtc: Implement -d option to write out a dependency file Jon Loeliger
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=4F1206F1.5090405@suse.cz \
--to=mmarek@suse.cz \
--cc=a-jacquiot@ti.com \
--cc=arnd@arndb.de \
--cc=benh@kernel.crashing.org \
--cc=david@gibson.dropbear.id.au \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=jdl@jdl.com \
--cc=jonas@southpole.se \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-c6x-dev@linux-c6x.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=linux@openrisc.net \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=microblaze-uclinux@itee.uq.edu.au \
--cc=monstr@monstr.eu \
--cc=msalter@redhat.com \
--cc=paulus@samba.org \
--cc=rob.herring@calxeda.com \
--cc=swarren@nvidia.com \
/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;
as well as URLs for NNTP newsgroup(s).