All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Gibson <david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org>
To: John Bonesio <bones-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
Cc: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
Subject: Re: dtc: Add code to make diffing trees easier
Date: Wed, 10 Nov 2010 11:55:03 +1100	[thread overview]
Message-ID: <20101110005503.GL30378@yookeroo> (raw)
In-Reply-To: <4CD9E122.7040707-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>

On Tue, Nov 09, 2010 at 04:02:42PM -0800, John Bonesio wrote:
> I just applied this patch and gave it a try.
> 
> I'm in the process of changing dts files for mpc5200b systems to use the
> new device tree merging with a .dtsi file.
> 
> I used this sorting tool to try to compare my results to make sure I'm
> not breaking anything. Unfortunately for some of the files I ended up
> renaming nodes from the original. When the nodes are renamed, the
> sorting doesn't produce what I would like. The nodes get reordered by
> the sorting method when in this case I'd rather they didn't change order.

> What I would have liked is to see that the node was renamed but the
> contents were the same.
> 
> I'm wondering if the node sorting could be done somehow by register
> values.

And then it won't generate what you want if you change reg, but leave
the name (mostly) the same.  Both methods are imperfect and the
current one is much simpler to implement, so, no.

-- 
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

  parent reply	other threads:[~2010-11-10  0:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-09 22:51 dtc: Add code to make diffing trees easier David Gibson
2010-11-10  0:02 ` John Bonesio
     [not found]   ` <4CD9E122.7040707-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
2010-11-10  0:55     ` David Gibson [this message]
2010-11-13 21:49 ` Jon Loeliger
  -- strict thread matches above, loose matches on Subject: below --
2010-10-11  0:37 David Gibson
2010-10-11  5:52 ` Grant Likely
     [not found]   ` <20101011055219.GK23588-MrY2KI0G/OVr83L8+7iqerDks+cytr/Z@public.gmane.org>
2010-10-11 14:23     ` Jon Loeliger
     [not found]       ` <E1P5JIE-0002Pw-J1-CYoMK+44s/E@public.gmane.org>
2010-10-11 16:09         ` Matthew McClintock
2010-10-12  2:08         ` 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=20101110005503.GL30378@yookeroo \
    --to=david-xt8fgy+axnrb3ne2bgzf6laj5h9x9tb+@public.gmane.org \
    --cc=bones-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org \
    --cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.