From: Michal Marek <mmarek@suse.cz>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: Russell King <linux@arm.linux.org.uk>,
nico@fluxnic.net, Haavard Skinnemoen <hskinnemoen@gmail.com>,
Hans-Christian Egtvedt <egtvedt@samfundet.no>,
Mike Frysinger <vapier@gentoo.org>,
Michal Simek <monstr@monstr.eu>, Paul Mundt <lethal@linux-sh.org>,
"David S. Miller" <davem@davemloft.net>,
Guan Xuetao <gxt@mprc.pku.edu.cn>,
linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
uclinux-dist-devel@blackfin.uclinux.org,
microblaze-uclinux@itee.uq.edu.au, linux-sh@vger.kernel.org,
sparclinux@vger.kernel.org, linux-arch@vger.kernel.org
Subject: Re: [PATCH] Kbuild: centralize MKIMAGE and cmd_uimage definitions
Date: Mon, 26 Mar 2012 15:48:42 +0200 [thread overview]
Message-ID: <4F7073BA.6040403@suse.cz> (raw)
In-Reply-To: <4F6B7226.8000102@wwwdotorg.org>
On 22.3.2012 19:40, Stephen Warren wrote:
> On 03/16/2012 03:03 PM, Stephen Warren wrote:
>> All ARCHs have the same definition of MKIMAGE. Move it to Makefile.lib
>> to avoid duplication.
>>
>> All ARCHs have similar definitions of cmd_uimage. Place a sufficiently
>> parameterized version in Makefile.lib to avoid duplication.
>
> Michal,
>
> Does this change look reasonable?
Absolutely.
> It has acks from people working on 4
> of the 7 affected architectures; would you prefer acks from all?
I will apply it now.
Michal
WARNING: multiple messages have this Message-ID (diff)
From: Michal Marek <mmarek@suse.cz>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: Russell King <linux@arm.linux.org.uk>,
nico@fluxnic.net, Haavard Skinnemoen <hskinnemoen@gmail.com>,
Hans-Christian Egtvedt <egtvedt@samfundet.no>,
Mike Frysinger <vapier@gentoo.org>,
Michal Simek <monstr@monstr.eu>, Paul Mundt <lethal@linux-sh.org>,
"David S. Miller" <davem@davemloft.net>,
Guan Xuetao <gxt@mprc.pku.edu.cn>,
linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
uclinux-dist-devel@blackfin.uclinux.org,
microblaze-uclinux@itee.uq.edu.au, linux-sh@vger.kernel.org,
sparclinux@vger.kernel.org, linux-arch@vger.kernel.org
Subject: Re: [PATCH] Kbuild: centralize MKIMAGE and cmd_uimage definitions
Date: Mon, 26 Mar 2012 13:48:42 +0000 [thread overview]
Message-ID: <4F7073BA.6040403@suse.cz> (raw)
In-Reply-To: <4F6B7226.8000102@wwwdotorg.org>
On 22.3.2012 19:40, Stephen Warren wrote:
> On 03/16/2012 03:03 PM, Stephen Warren wrote:
>> All ARCHs have the same definition of MKIMAGE. Move it to Makefile.lib
>> to avoid duplication.
>>
>> All ARCHs have similar definitions of cmd_uimage. Place a sufficiently
>> parameterized version in Makefile.lib to avoid duplication.
>
> Michal,
>
> Does this change look reasonable?
Absolutely.
> It has acks from people working on 4
> of the 7 affected architectures; would you prefer acks from all?
I will apply it now.
Michal
WARNING: multiple messages have this Message-ID (diff)
From: mmarek@suse.cz (Michal Marek)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] Kbuild: centralize MKIMAGE and cmd_uimage definitions
Date: Mon, 26 Mar 2012 15:48:42 +0200 [thread overview]
Message-ID: <4F7073BA.6040403@suse.cz> (raw)
In-Reply-To: <4F6B7226.8000102@wwwdotorg.org>
On 22.3.2012 19:40, Stephen Warren wrote:
> On 03/16/2012 03:03 PM, Stephen Warren wrote:
>> All ARCHs have the same definition of MKIMAGE. Move it to Makefile.lib
>> to avoid duplication.
>>
>> All ARCHs have similar definitions of cmd_uimage. Place a sufficiently
>> parameterized version in Makefile.lib to avoid duplication.
>
> Michal,
>
> Does this change look reasonable?
Absolutely.
> It has acks from people working on 4
> of the 7 affected architectures; would you prefer acks from all?
I will apply it now.
Michal
next prev parent reply other threads:[~2012-03-26 13:48 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-16 21:03 [PATCH] Kbuild: centralize MKIMAGE and cmd_uimage definitions Stephen Warren
2012-03-16 21:03 ` Stephen Warren
2012-03-16 21:03 ` Stephen Warren
2012-03-16 21:47 ` Nicolas Pitre
2012-03-16 21:47 ` Nicolas Pitre
2012-03-16 21:47 ` Nicolas Pitre
2012-03-19 0:42 ` Mike Frysinger
2012-03-19 0:42 ` Mike Frysinger
2012-03-19 0:42 ` Mike Frysinger
2012-03-19 6:46 ` Michal Simek
2012-03-19 6:46 ` Michal Simek
2012-03-19 6:46 ` Michal Simek
2012-03-19 9:05 ` Guan Xueao
2012-03-19 9:05 ` Guan Xueao
2012-03-19 9:05 ` Guan Xueao
2012-03-22 18:40 ` Stephen Warren
2012-03-22 18:40 ` Stephen Warren
2012-03-22 18:40 ` Stephen Warren
2012-03-22 20:53 ` Mike Frysinger
2012-03-22 20:53 ` Mike Frysinger
2012-03-22 20:53 ` Mike Frysinger
2012-03-26 13:48 ` Michal Marek [this message]
2012-03-26 13:48 ` Michal Marek
2012-03-26 13:48 ` 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=4F7073BA.6040403@suse.cz \
--to=mmarek@suse.cz \
--cc=davem@davemloft.net \
--cc=egtvedt@samfundet.no \
--cc=gxt@mprc.pku.edu.cn \
--cc=hskinnemoen@gmail.com \
--cc=lethal@linux-sh.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=microblaze-uclinux@itee.uq.edu.au \
--cc=monstr@monstr.eu \
--cc=nico@fluxnic.net \
--cc=sparclinux@vger.kernel.org \
--cc=swarren@wwwdotorg.org \
--cc=uclinux-dist-devel@blackfin.uclinux.org \
--cc=vapier@gentoo.org \
/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.