From: Michal Marek <mmarek@suse.cz>
To: Stephen Warren <swarren@nvidia.com>
Cc: Mark Salter <msalter@redhat.com>, 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-kbuild@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-c6x-dev@linux-c6x.org" <linux-c6x-dev@linux-c6x.org>,
"microblaze-uclinux@itee.uq.edu.au"
<microblaze-uclinux@itee.uq.edu.au>,
"linux@openrisc.net" <linux@openrisc.net>,
"linuxppc-dev@lists.ozlabs.org" <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: Wed, 18 Jan 2012 11:07:58 +0100 [thread overview]
Message-ID: <4F1699FE.5050005@suse.cz> (raw)
In-Reply-To: <74CDBE0F657A3D45AFBB94109FB122FF17801D2255@HQMAIL01.nvidia.com>
On 17.1.2012 18:20, Stephen Warren wrote:
> Michal Marek wrote at Saturday, January 14, 2012 3:51 PM:
>> 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?
OK, that was a misunderstanding then. I applied it to the kbuild branch
for 3.3 and Linus pulled it in the meantime. It's not a terribly
intrusive change, after all.
Michal
WARNING: multiple messages have this Message-ID (diff)
From: Michal Marek <mmarek@suse.cz>
To: Stephen Warren <swarren@nvidia.com>
Cc: 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>,
Devicetree Discuss <devicetree-discuss@lists.ozlabs.org>,
"microblaze-uclinux@itee.uq.edu.au"
<microblaze-uclinux@itee.uq.edu.au>,
"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>,
Mark Salter <msalter@redhat.com>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"linux@openrisc.net" <linux@openrisc.net>,
"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: Wed, 18 Jan 2012 11:07:58 +0100 [thread overview]
Message-ID: <4F1699FE.5050005@suse.cz> (raw)
In-Reply-To: <74CDBE0F657A3D45AFBB94109FB122FF17801D2255@HQMAIL01.nvidia.com>
On 17.1.2012 18:20, Stephen Warren wrote:
> Michal Marek wrote at Saturday, January 14, 2012 3:51 PM:
>> 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?
OK, that was a misunderstanding then. I applied it to the kbuild branch
for 3.3 and Linus pulled it in the meantime. It's not a terribly
intrusive change, after all.
Michal
WARNING: multiple messages have this Message-ID (diff)
From: mmarek@suse.cz (Michal Marek)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] Kbuild: Use dtc's -d (dependency) option
Date: Wed, 18 Jan 2012 11:07:58 +0100 [thread overview]
Message-ID: <4F1699FE.5050005@suse.cz> (raw)
In-Reply-To: <74CDBE0F657A3D45AFBB94109FB122FF17801D2255@HQMAIL01.nvidia.com>
On 17.1.2012 18:20, Stephen Warren wrote:
> Michal Marek wrote at Saturday, January 14, 2012 3:51 PM:
>> 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?
OK, that was a misunderstanding then. I applied it to the kbuild branch
for 3.3 and Linus pulled it in the meantime. It's not a terribly
intrusive change, after all.
Michal
WARNING: multiple messages have this Message-ID (diff)
From: Michal Marek <mmarek@suse.cz>
To: Stephen Warren <swarren@nvidia.com>
Cc: 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>,
Devicetree Discuss <devicetree-discuss@lists.ozlabs.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
"microblaze-uclinux@itee.uq.edu.au"
<microblaze-uclinux@itee.uq.edu.au>,
"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>,
Grant Likely <grant.likely@secretlab.ca>,
Paul Mackerras <paulus@samba.org>,
Mark Salter <msalter@redhat.com>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"linux@openrisc.net" <linux@openrisc.net>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
David
Subject: Re: [PATCH 2/2] Kbuild: Use dtc's -d (dependency) option
Date: Wed, 18 Jan 2012 11:07:58 +0100 [thread overview]
Message-ID: <4F1699FE.5050005@suse.cz> (raw)
In-Reply-To: <74CDBE0F657A3D45AFBB94109FB122FF17801D2255@HQMAIL01.nvidia.com>
On 17.1.2012 18:20, Stephen Warren wrote:
> Michal Marek wrote at Saturday, January 14, 2012 3:51 PM:
>> 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?
OK, that was a misunderstanding then. I applied it to the kbuild branch
for 3.3 and Linus pulled it in the meantime. It's not a terribly
intrusive change, after all.
Michal
next prev parent reply other threads:[~2012-01-18 10:08 UTC|newest]
Thread overview: 38+ 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 ` Stephen Warren
2012-01-09 18:38 ` Stephen Warren
2012-01-09 18:38 ` Stephen Warren
2012-01-09 18:38 ` Stephen Warren
2012-01-09 18:38 ` [PATCH 2/2] Kbuild: Use dtc's -d (dependency) option Stephen Warren
2012-01-09 18:38 ` Stephen Warren
2012-01-09 18:38 ` Stephen Warren
2012-01-09 18:38 ` Stephen Warren
2012-01-09 18:38 ` Stephen Warren
2012-01-10 3:12 ` Shawn Guo
2012-01-10 3:12 ` Shawn Guo
2012-01-10 3:12 ` Shawn Guo
2012-01-10 3:12 ` Shawn Guo
2012-01-11 19:36 ` Mark Salter
2012-01-11 19:36 ` Mark Salter
2012-01-11 19:36 ` Mark Salter
2012-01-11 19:36 ` Mark Salter
2012-01-14 22:51 ` Michal Marek
2012-01-14 22:51 ` Michal Marek
2012-01-14 22:51 ` Michal Marek
2012-01-17 17:20 ` Stephen Warren
2012-01-17 17:20 ` Stephen Warren
2012-01-17 17:20 ` Stephen Warren
2012-01-17 17:20 ` Stephen Warren
2012-01-17 18:26 ` Mark Salter
2012-01-17 18:26 ` Mark Salter
2012-01-17 18:26 ` Mark Salter
2012-01-17 18:26 ` Mark Salter
2012-01-18 10:07 ` Michal Marek [this message]
2012-01-18 10:07 ` Michal Marek
2012-01-18 10:07 ` Michal Marek
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
2012-01-09 18:58 ` Jon Loeliger
2012-01-09 18:58 ` Jon Loeliger
2012-01-09 18:58 ` Jon Loeliger
2012-01-09 18:58 ` 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=4F1699FE.5050005@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.