From: Mark Salter <msalter@redhat•com>
To: Stephen Warren <swarren@nvidia•com>
Cc: Michal Marek <mmarek@suse•cz>, Jonas Bonn <jonas@southpole•se>,
Jon Loeliger <jdl@jdl•com>, Russell King <linux@arm•linux.org.uk>,
"linux-c6x-dev@linux-c6x•org" <linux-c6x-dev@linux-c6x•org>,
Arnd Bergmann <arnd@arndb•de>,
Aurelien Jacquiot <a-jacquiot@ti•com>,
"linux@openrisc•net" <linux@openrisc•net>,
"linux-kbuild@vger•kernel.org" <linux-kbuild@vger•kernel.org>,
Michal Simek <monstr@monstr•eu>,
Rob Herring <rob.herring@calxeda•com>,
"linux-kernel@vger•kernel.org" <linux-kernel@vger•kernel.org>,
Paul Mackerras <paulus@samba•org>,
"microblaze-uclinux@itee•uq.edu.au"
<microblaze-uclinux@itee•uq.edu.au>,
"linuxppc-dev@lists•ozlabs.org" <linuxppc-dev@lists•ozlabs.org>,
Devicetree Discuss <devicetree-discuss@lists•ozlabs.org>,
"linux-arm-kernel@lists•infradead.org"
<linux-arm-kernel@lists•infradead.org>,
David Gibson <david@gibson•dropbear.id.au>
Subject: RE: [PATCH 2/2] Kbuild: Use dtc's -d (dependency) option
Date: Tue, 17 Jan 2012 13:26:06 -0500 [thread overview]
Message-ID: <1326824773.20239.12.camel@deneb.redhat.com> (raw)
In-Reply-To: <74CDBE0F657A3D45AFBB94109FB122FF17801D2255@HQMAIL01.nvidia.com>
On Tue, 2012-01-17 at 09:20 -0800, Stephen Warren wrote:
> Michal Marek wrote at Saturday, January 14, 2012 3:51 PM:
> > 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?
>
> I was assuming my patches were for 3.4 rather than 3.3, since it's pretty
> late for new features in 3.3. In that case, there wouldn't be an issue,
> right?
>
> If you do want to go ahead and push my patches into 3.3, your proposal
> looks fine to me. Mark, do you want me to push the patch to Linus, or
> do you want to pick it up?
It would probably be best to keep it all together, but if there's a need
to break out c6x individually, I don't mind picking it up.
--Mark
next prev parent reply other threads:[~2012-01-17 18:26 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
2012-01-17 17:20 ` Stephen Warren
2012-01-17 18:26 ` Mark Salter [this message]
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=1326824773.20239.12.camel@deneb.redhat.com \
--to=msalter@redhat$(echo .)com \
--cc=a-jacquiot@ti$(echo .)com \
--cc=arnd@arndb$(echo .)de \
--cc=david@gibson$(echo .)dropbear.id.au \
--cc=devicetree-discuss@lists$(echo .)ozlabs.org \
--cc=jdl@jdl$(echo .)com \
--cc=jonas@southpole$(echo .)se \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-c6x-dev@linux-c6x$(echo .)org \
--cc=linux-kbuild@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux@arm$(echo .)linux.org.uk \
--cc=linux@openrisc$(echo .)net \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=microblaze-uclinux@itee$(echo .)uq.edu.au \
--cc=mmarek@suse$(echo .)cz \
--cc=monstr@monstr$(echo .)eu \
--cc=paulus@samba$(echo .)org \
--cc=rob.herring@calxeda$(echo .)com \
--cc=swarren@nvidia$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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