From: David Gibson <david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org>
To: Jon Loeliger <jdl-CYoMK+44s/E@public.gmane.org>
Cc: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
Subject: Re: [PATCH v3] Allow device tree to be modified by additonal device tree sections
Date: Fri, 26 Feb 2010 11:25:54 +1100 [thread overview]
Message-ID: <20100226002554.GI31576@yookeroo> (raw)
In-Reply-To: <E1Nkhq1-0001Of-Hb-CYoMK+44s/E@public.gmane.org>
On Thu, Feb 25, 2010 at 11:49:25AM -0600, Jon Loeliger wrote:
> > This patch allows the following construct:
> >
> > / {
> > property-a = "old";
> > property-b = "does not change";
> > };
> >
> > / {
> > property-a = "changed";
> > property-c = "new";
> > node-a {
> > };
> > };
> >
> > Where the later device tree overrides the properties found in the
> > earlier tree. This is useful for laying down a template device tree
> > in an include file and modifying it for a specific board without having
> > to clone the entire tree.
> >
> > Signed-off-by: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
>
> Applied.
Oops, I was hoping to make a few tweaks to that before it was
applied. Oh well, it was basically only more thorough testcases, so
that can be added later.
Sorry Grant, my work on this stuff has been rather delayed by
yak-shaving.
--
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
next prev parent reply other threads:[~2010-02-26 0:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-25 16:58 [PATCH v3] Allow device tree to be modified by additonal device tree sections Grant Likely
2010-02-25 17:49 ` Jon Loeliger
[not found] ` <E1Nkhq1-0001Of-Hb-CYoMK+44s/E@public.gmane.org>
2010-02-26 0:25 ` David Gibson [this message]
2010-02-26 14:06 ` Jon Loeliger
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=20100226002554.GI31576@yookeroo \
--to=david-xt8fgy+axnrb3ne2bgzf6laj5h9x9tb+@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=jdl-CYoMK+44s/E@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.