From: Hollis Blanchard <hollis@penguinppc.org>
To: Jon Loeliger <jdl@freescale.com>
Cc: linuxppc-dev <Linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH 1/1] bootwrapper: add flat device tree support code
Date: Mon, 11 Sep 2006 13:44:05 -0500 [thread overview]
Message-ID: <1158000245.24546.24.camel@basalt.austin.ibm.com> (raw)
In-Reply-To: <1157995667.27129.148.camel@cashmere.sps.mot.com>
On Mon, 2006-09-11 at 12:27 -0500, Jon Loeliger wrote:
>
> Wasn't there a notion of even combining this with
> the DTC code base directly? I haven't seen any
> patches or motion down this line, though...?
That's certainly a good place the new code could be applied. Of course,
I haven't sent patches to uboot, iseries boot code, kexec, or any other
number of places either, and don't really plan to. If those areas have
problems, they can switch to the consolidated codebase then (rather than
bugfixing the non-consolidated code).
Why, are you going to convert DTC?
-Hollis
next prev parent reply other threads:[~2006-09-11 18:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-08 3:46 [PATCH 1/1] bootwrapper: add flat device tree support code Mark A. Greer
2006-09-08 14:46 ` Hollis Blanchard
2006-09-08 16:52 ` Mark A. Greer
2006-09-11 17:27 ` Jon Loeliger
2006-09-11 18:44 ` Hollis Blanchard [this message]
2006-09-11 18:39 ` Jon Loeliger
2006-09-11 19:01 ` Hollis Blanchard
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=1158000245.24546.24.camel@basalt.austin.ibm.com \
--to=hollis@penguinppc.org \
--cc=Linuxppc-dev@ozlabs.org \
--cc=jdl@freescale.com \
/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).