linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Jon Loeliger <jdl@jdl.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: dtc: Merge refs and labels into single "markers" list
Date: Mon, 26 Nov 2007 16:11:52 -0600	[thread overview]
Message-ID: <E1IwmBE-0002f5-L2@jdl.com> (raw)
In-Reply-To: Your message of "Thu, 22 Nov 2007 11:37:07 +1100." <20071122003707.GF19445@localhost.localdomain>

So, like, the other day David Gibson mumbled:
> Currently, every 'data' object, used to represent property values, has
> two lists of fixup structures - one for labels and one for references.
> Sometimes we want to look at them separately, but other times we need
> to consider both types of fixup.
> 
> I'm planning to implement string references, where a full path rather
> than a phandle is substituted into a property value.  Adding yet
> another list of fixups for that would start to get messy.  So, this
> patch merges the "refs" and "labels" lists into a single list of
> "markers", each of which has a type field indicating if it represents
> a label or a phandle reference.  String references or any other new
> type of in-data marker will then just need a new type value - merging
> data blocks and other common manipulations will just work.
> 
> While I was at it I made some cleanups to the handling of fixups which
> simplify things further.
> 
> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>

Applied.

Thanks,
jdl

      parent reply	other threads:[~2007-11-26 22:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-22  0:37 dtc: Merge refs and labels into single "markers" list David Gibson
2007-11-22  3:39 ` dtc: Merge refs and labels into single "markers" list (v2) David Gibson
2007-11-26 22:11 ` Jon Loeliger [this message]

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=E1IwmBE-0002f5-L2@jdl.com \
    --to=jdl@jdl.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).