public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Marian Balakowicz <m8@semihalf.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH 6/8] libfdt: Add and use a node iteration helper function.
Date: Mon, 03 Mar 2008 10:21:32 +0100	[thread overview]
Message-ID: <47CBC31C.9030707@semihalf.com> (raw)
In-Reply-To: <47C9A850.8020404@gmail.com>


Hi Jerry,

Jerry Van Baren wrote:
> Marian Balakowicz wrote:
>> From: David Gibson <david@gibson.dropbear.id.au>
>>
>> This patch adds an fdt_next_node() function which can be used to
>> iterate through nodes of the tree while keeping track of depth.  This
>> function is used to simplify the iteration code in a lot of other
>> functions, and is also exported for use by library users.
>>
>> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
>> ---
>>
>>  include/libfdt.h |    6 +
>>  libfdt/fdt.c     |   41 +++++++++
>>  libfdt/fdt_ro.c  |  258
>> ++++++++++++++++++------------------------------------
>>  3 files changed, 131 insertions(+), 174 deletions(-)
> 
...
> I've picked up this patchset, along with two other libfdt patchsets, in
> the u-boot-fdt subrepo.  I am holding back the changes for the next
> merge window.
> 
> <http://www.denx.de/cgi-bin/gitweb.cgi?p=u-boot/u-boot-fdt.git;a=commit;h=162fa0021d04495f1e514d2b50f28dddd031f688>
> 
> 
> Did you cherry-pick this out of the u-boot-fdt subrepo or apply it
> yourself from David's patch?
> 
> I don't know how git will react if we both apply the same patch,
> possibly differently.  (I applied it by hand editing the patch to change
> the include/libfdt.h path and then using git-am to apply it.  I presume
> you either cherry-picked my application or did the same.)

I've seen the patch on the ml, but than noticed it's already in the
custodian repo, so I took the easier approach and cherry picked from
u-boot-fdt.

Cheers,
m.

  reply	other threads:[~2008-03-03  9:21 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-29 23:19 [U-Boot-Users] [PATCH 0/8] [new uImage] patchset6 - new uImage format low level API Marian Balakowicz
2008-02-29 23:19 ` [U-Boot-Users] [PATCH 1/8] [new uImage] Update naming convention for bootm/uImage related code Marian Balakowicz
2008-02-29 23:19 ` [U-Boot-Users] [PATCH 2/8] [new uImage] Share common uImage code between mkimage and U-boot Marian Balakowicz
2008-02-29 23:19 ` [U-Boot-Users] [PATCH 3/8] [new uImage] Fix component handling for legacy multi component images Marian Balakowicz
2008-02-29 23:19 ` [U-Boot-Users] [PATCH 4/8] [new uImage] Add sha1.o object to mkimage binary build Marian Balakowicz
2008-02-29 23:19 ` [U-Boot-Users] [PATCH 5/8] [new uImage] Add libfdt support to mkimage Marian Balakowicz
2008-03-01 20:32   ` Jerry Van Baren
2008-03-03 10:01     ` Marian Balakowicz
2008-03-03 14:29     ` Jon Loeliger
2008-02-29 23:19 ` [U-Boot-Users] [PATCH 6/8] libfdt: Add and use a node iteration helper function Marian Balakowicz
2008-03-01 19:02   ` Jerry Van Baren
2008-03-03  9:21     ` Marian Balakowicz [this message]
2008-03-03 13:14       ` Jerry Van Baren
2008-02-29 23:20 ` [U-Boot-Users] [PATCH 7/8] [new uImage] Fix FDT blob totalsize calculation in boot_relocate_fdt() Marian Balakowicz
2008-02-29 23:20 ` [U-Boot-Users] [PATCH 8/8] [new uImage] New uImage low-level API Marian Balakowicz

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=47CBC31C.9030707@semihalf.com \
    --to=m8@semihalf.com \
    --cc=u-boot@lists.denx.de \
    /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