From: monstr@monstr.eu (Michal Simek)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] Kbuild: centralize MKIMAGE and cmd_uimage definitions
Date: Mon, 19 Mar 2012 07:46:10 +0100 [thread overview]
Message-ID: <4F66D632.5070107@monstr.eu> (raw)
In-Reply-To: <1331931835-12346-1-git-send-email-swarren@wwwdotorg.org>
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.
>
> Signed-off-by: Stephen Warren <swarren@wwwdotorg.org>
> ---
> v2:
> * Fix blackfin's UIMAGE_LOADADDR in the ROMKERNEL case.
> * Fix missing ) on a variable reference in avr32 and sparc.
> * Only set those UIMAGE_* variables that the arch-specific Makefile hasn't
> already set.
> * The patch series is now just this single patch which removes duplication;
> I've dropped the Kconfig feature to allow use of -T kernel_noload for
> now, since it looks like U-Boot is gaining direct zImage support.
>
> arch/arm/boot/Makefile | 23 +++++++++--------------
> arch/avr32/boot/images/Makefile | 9 +++------
> arch/blackfin/boot/Makefile | 19 ++++++++-----------
> arch/microblaze/boot/Makefile | 10 +++-------
> arch/sh/boot/Makefile | 8 ++------
> arch/sparc/boot/Makefile | 9 +++------
> arch/unicore32/boot/Makefile | 12 ++----------
> scripts/Makefile.lib | 24 ++++++++++++++++++++++++
> 8 files changed, 54 insertions(+), 60 deletions(-)
No problem for Microblaze.
Tested-by: Michal Simek <monstr@monstr.eu>
Thanks,
Michal
--
Michal Simek, Ing. (M.Eng)
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel 2.6 Microblaze Linux - http://www.monstr.eu/fdt/
Microblaze U-BOOT custodian
next prev parent reply other threads:[~2012-03-19 6:46 UTC|newest]
Thread overview: 8+ 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:47 ` Nicolas Pitre
2012-03-19 0:42 ` Mike Frysinger
2012-03-19 6:46 ` Michal Simek [this message]
2012-03-19 9:05 ` Guan Xueao
2012-03-22 18:40 ` Stephen Warren
2012-03-22 20:53 ` Mike Frysinger
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=4F66D632.5070107@monstr.eu \
--to=monstr@monstr.eu \
--cc=linux-arm-kernel@lists.infradead.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 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).