Devicetree
 help / color / mirror / Atom feed
From: David Gibson <david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org>
To: Jon Loeliger <jdl-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
Cc: devicetree-discuss-mnsaURCQ41sdnm+yROfE0A@public.gmane.org
Subject: [0/2] libfdt: Cleanups to iteration functions
Date: Tue, 11 Nov 2008 23:18:04 +1100	[thread overview]
Message-ID: <20081111121804.GH26376@yookeroo.seuss> (raw)

These two patches make some cleanups to the fdt_next_node() and
fdt_next_tag() functions that I've been meaning to do for a while.

These patches do introduce minor semantic changes, and those are
exported functions.  I think they're still reasonable changes, because
the behavioural changes are in corner cases which previously had
somewhat fuzzily defined semantics anyway.  I would be very doubtful
that anyway was relying on the altered behaviour; if I'm wrong about
that these patches could need some rethinking.

These cleanups make it easier to implement property iteration, which I
have a draft patch for in the works.  I'm not posting that with this
series, because I'm having second thoughts about the details of the
interface, and I need to write some testcases.  I'll try to post that
as an RFC / work-in-progress shortly.

-- 
David Gibson			| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you.  NOT _the_ _other_
				| _way_ _around_!
http://www.ozlabs.org/~dgibson

             reply	other threads:[~2008-11-11 12:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-11 12:18 David Gibson [this message]
     [not found] ` <20081111121804.GH26376-787xzQ0H9iRg7VrjXcPTGA@public.gmane.org>
2008-11-11 12:19   ` [1/2] libfdt: Rework fdt_next_node() David Gibson
     [not found]     ` <20081111121936.GI26376-787xzQ0H9iRg7VrjXcPTGA@public.gmane.org>
2008-11-11 12:21       ` [2/2] libfdt: Rework/cleanup fdt_next_tag() David Gibson

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=20081111121804.GH26376@yookeroo.seuss \
    --to=david-xt8fgy+axnrb3ne2bgzf6laj5h9x9tb+@public.gmane.org \
    --cc=devicetree-discuss-mnsaURCQ41sdnm+yROfE0A@public.gmane.org \
    --cc=jdl-KZfg59tc24xl57MIdRCFDg@public.gmane.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