linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Hollis Blanchard <hollis@penguinppc.org>
To: "Mark A. Greer" <mgreer@mvista.com>
Cc: linuxppc-dev <Linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH 0/6] bootwrapper: arch/powerpc/boot code reorg patches
Date: Tue, 15 Aug 2006 14:37:06 -0500	[thread overview]
Message-ID: <1155670626.6338.3.camel@basalt.austin.ibm.com> (raw)
In-Reply-To: <20060808191450.GA10108@mag.az.mvista.com>

On Tue, 2006-08-08 at 12:14 -0700, Mark A. Greer wrote:
> Just a note that I will respin my patches to address all of your
> comments.  However, it looks like the fdt code is going to change
> to use code from a common source base.  I'm going to wait until
> that has settled and then I'll modify the code and repost the patches.

By the way, I don't expect the (ft_build.h) interface to change much
from what I emailed last week. So I think it's safe to build on top of
those.

The only addition I'd like to make is creating an ft_set_prop() that
will handle resizing the tree for you. With that change, you wouldn't
ft_get_prop() and then write directly to that pointer (as is done
currently).

I'm still waiting to hear the outcome of Matt's patches. I don't need
them, but if u-boot does then I'll have to merge them into the
standalone code.

-Hollis

  reply	other threads:[~2006-08-15 19:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-19 22:53 [PATCH 0/6] bootwrapper: arch/powerpc/boot code reorg patches Mark A. Greer
2006-07-22 15:04 ` Tom Rini
2006-08-08 19:14 ` Mark A. Greer
2006-08-15 19:37   ` Hollis Blanchard [this message]
2006-08-18 21:46     ` Mark A. Greer
2006-08-18 21:41       ` Jon Loeliger
2006-09-08  3:32 ` Mark A. Greer

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=1155670626.6338.3.camel@basalt.austin.ibm.com \
    --to=hollis@penguinppc.org \
    --cc=Linuxppc-dev@ozlabs.org \
    --cc=mgreer@mvista.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).