From: Jon Loeliger <jdl@freescale.com>
To: Jerry Van Baren <gerald.vanbaren@smiths-aerospace.com>
Cc: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>,
Jon Loeliger <jdl@jdl.com>,
u-boot-users <u-boot-users@lists.sourceforge.net>
Subject: Re: [U-Boot-Users] [PATCH: dtc take 2] Assemble the blob in memory before writing it out.
Date: Thu, 19 Apr 2007 14:03:15 -0500 [thread overview]
Message-ID: <1177009395.14328.29.camel@ld0161-tx32> (raw)
In-Reply-To: <4627B9C7.8010800@smiths-aerospace.com>
On Thu, 2007-04-19 at 13:49, Jerry Van Baren wrote:
> >
> > Sorry. I've been out sick for a couple days here and am
> > just now catching up. I've read through the last week's
> > worth of mail here now, so let me see if I have properly
> > summarized where things stand and what's needed for the DTC:
> >
> > These patches need to be applied:
> >
> > [PATCH dtc] Add -o <output file> to the usage message.
> > Sat, 14 Apr 2007 18:16:47 -0400
> >
> > [PATCH dtc take 3] Fix reserve map output for asm format.
> > Tue, 17 Apr 2007 18:14:41 -0400
> >
> > [PATCH: dtc take 2] Assemble the blob in memory before writing it out.
> > Wed, 18 Apr 2007 21:59:51 -0400
> >
> > The last patch there replaces the "Improve -S handling" patches.
> > But does the last patch replace or depend on the second one?
> >
> > And I agree with David that last patch is a better approach.
> >
> > Thanks,
> > jdl
>
> Yes, you have that right.
Good. The drugs aren't too strong yet. :-)
> Patch #1 is good to go
> [PATCH dtc] Add -o <output file> to the usage message.
> Sat, 14 Apr 2007 18:16:47 -0400
>
> Patch #2 and #3...
> [PATCH dtc take 3] Fix reserve map output for asm format.
> Tue, 17 Apr 2007 18:14:41 -0400
> [PATCH: dtc take 2] Assemble the blob in memory before writing it out.
> Wed, 18 Apr 2007 21:59:51 -0400
>
> ...you force me to make a confession.
It's good for the soul. :-)
> Your option:
> 1) Take the last two patches as is and remove the fprintf yourself
> 2) I'll fix it tonight and provide a New Improved patch
I'll go with Door Number 1! No problem.
Thanks,
jdl
next prev parent reply other threads:[~2007-04-19 19:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-19 1:59 [PATCH: dtc take 2] Assemble the blob in memory before writing it out Jerry Van Baren
2007-04-19 2:05 ` David Gibson
2007-04-19 18:27 ` Jon Loeliger
2007-04-19 18:49 ` [U-Boot-Users] " Jerry Van Baren
2007-04-19 19:03 ` Jon Loeliger [this message]
2007-04-19 22:31 ` Jon Loeliger
2007-04-19 23:45 ` Jerry Van Baren
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=1177009395.14328.29.camel@ld0161-tx32 \
--to=jdl@freescale.com \
--cc=gerald.vanbaren@smiths-aerospace.com \
--cc=jdl@jdl.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=u-boot-users@lists.sourceforge.net \
/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).