From: Sam Ravnborg <sam@ravnborg.org>
To: Josh Boyer <jwboyer@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, paulus@samba.org
Subject: Re: [RFC] [PATCH 2/3] Rework arch specific Makefiles to use mkimage
Date: Sat, 5 Jan 2008 21:17:28 +0100 [thread overview]
Message-ID: <20080105201728.GA9985@uranus.ravnborg.org> (raw)
In-Reply-To: <20071220101829.44ca59da@zod.rchland.ibm.com>
On Thu, Dec 20, 2007 at 10:18:29AM -0600, Josh Boyer wrote:
> Rework the architecture specific Makefiles to use the in-kernel version
> of the mkimage tool.
>
> Signed-off-by: Josh Boyer <jwboyer@linux.vnet.ibm.com>
>
> ---
> arch/arm/boot/Makefile | 4 ++--
> arch/avr32/boot/images/Makefile | 4 ++--
> arch/blackfin/boot/Makefile | 4 ++--
> arch/powerpc/boot/Makefile | 8 ++++++--
> arch/powerpc/boot/wrapper | 2 +-
> arch/ppc/boot/images/Makefile | 4 ++--
> arch/sh/boot/Makefile | 4 ++--
> 7 files changed, 17 insertions(+), 13 deletions(-)
>
> --- linux-2.6.orig/arch/arm/boot/Makefile
> +++ linux-2.6/arch/arm/boot/Makefile
> @@ -11,7 +11,7 @@
> # Copyright (C) 1995-2002 Russell King
> #
>
> -MKIMAGE := $(srctree)/scripts/mkuboot.sh
> +MKIMAGE := $(srctree)/scripts/mkimage/mkimage
I did s/srctree/objtree/ for all these assignments - as mkimage
is a generated file which is not present in $(srctree) for
make O=... builds.
Sam
next prev parent reply other threads:[~2008-01-05 20:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-20 16:16 [RFC] Merge mkimage tool Josh Boyer
2007-12-20 16:17 ` [RFC] [PATCH 1/3] Merge mkimage tool for building uImages Josh Boyer
2007-12-20 18:36 ` H. Peter Anvin
2007-12-20 19:41 ` Josh Boyer
2007-12-20 16:18 ` [RFC] [PATCH 2/3] Rework arch specific Makefiles to use mkimage Josh Boyer
2007-12-21 1:02 ` Mike Frysinger
2007-12-21 1:20 ` Josh Boyer
2008-01-05 20:17 ` Sam Ravnborg [this message]
2007-12-20 16:19 ` [RFC] [PATCH 3/3] Remove mkuboot.sh script Josh Boyer
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=20080105201728.GA9985@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=jwboyer@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.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
Powered by JetHome