From: "H. Peter Anvin" <hpa@zytor.com>
To: Josh Boyer <jwboyer@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, paulus@samba.org
Subject: Re: [RFC] [PATCH 1/3] Merge mkimage tool for building uImages
Date: Thu, 20 Dec 2007 10:36:48 -0800 [thread overview]
Message-ID: <476AB640.4040005@zytor.com> (raw)
In-Reply-To: <20071220101739.45b28d26@zod.rchland.ibm.com>
Josh Boyer wrote:
> Several platforms require the mkimage tool to generate a uImage file
> that is used with U-Boot. This brings the mkimage tool in-kernel to
> enable building those platforms without having mkimage internally
> provided.
>
> This is currently based off of the version found in U-Boot 1.3.1.
>
Can we rename it either "ubootimage" or "mkuboot" or something else that
tells the user what kind of image it is? (It is, in particular, not
bzImage, which is probably the first thing that someone who sees "image"
in a arch-generic part of the Linux kernel tree will think.)
-hpa
next prev parent reply other threads:[~2007-12-20 18:44 UTC|newest]
Thread overview: 10+ 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 [this message]
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
2007-12-20 16:19 ` [RFC] [PATCH 3/3] Remove mkuboot.sh script Josh Boyer
-- strict thread matches above, loose matches on Subject: below --
2007-12-19 16:33 [RFC] Merge mkimage tool Josh Boyer
2007-12-19 16:35 ` [RFC] [PATCH 1/3] Merge mkimage tool for building uImages 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=476AB640.4040005@zytor.com \
--to=hpa@zytor.com \
--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 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.