From: Matthew McClintock <msm@freescale.com>
To: Li Yang-r58472 <LeoLi@freescale.com>
Cc: linuxppc-dev <Linuxppc-dev@ozlabs.org>
Subject: RE: [RFC] New target 'cuImage' - compatibility uImage
Date: Thu, 03 Aug 2006 10:30:13 -0500 [thread overview]
Message-ID: <1154619014.5094.7.camel@localhost> (raw)
In-Reply-To: <4879B0C6C249214CBE7AB04453F84E4D0B2F61@zch01exm20.fsl.freescale.net>
On Thu, 2006-08-03 at 04:47 -0700, Li Yang-r58472 wrote:
> If my understanding to Matt's idea is correct, it will be a good way,
> IMHO. How about use the naming of uwImage(U-boot Wrapped Image) or
> utImage(u-boot device-Tree Image).
I am completely open to a better name. Anyone else care to share their
opinion?
-Matthew
next prev parent reply other threads:[~2006-08-03 15:30 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-02 20:59 [RFC] New target 'cuImage' - compatibility uImage Matthew McClintock
2006-08-02 22:33 ` Wolfgang Denk
2006-08-03 11:38 ` Li Yang-r58472
2006-08-03 15:29 ` Matthew McClintock
2006-08-03 15:56 ` Li Yang
2006-08-03 16:02 ` Matthew McClintock
2006-08-03 16:17 ` Li Yang
2006-08-03 16:24 ` Matthew McClintock
2006-08-03 16:47 ` Li Yang
2006-08-03 20:14 ` Wolfgang Denk
2006-08-03 20:20 ` Matthew McClintock
2006-08-03 20:25 ` Wolfgang Denk
2006-08-03 20:40 ` Matthew McClintock
2006-08-03 20:07 ` Wolfgang Denk
2006-08-03 19:37 ` Mark A. Greer
2006-08-03 20:02 ` Wolfgang Denk
2006-08-03 20:00 ` Wolfgang Denk
2006-08-03 20:12 ` Matthew McClintock
2006-08-03 20:23 ` Wolfgang Denk
2006-08-03 20:31 ` Matthew McClintock
2006-08-03 0:30 ` Tom Rini
2006-08-03 15:24 ` Matthew McClintock
2006-08-03 11:47 ` Li Yang-r58472
2006-08-03 15:30 ` Matthew McClintock [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-08-03 9:29 Milton Miller
2006-08-03 18:17 Milton Miller
2006-08-03 18:53 ` Matthew McClintock
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=1154619014.5094.7.camel@localhost \
--to=msm@freescale.com \
--cc=LeoLi@freescale.com \
--cc=Linuxppc-dev@ozlabs.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).