devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Jon Loeliger <jdl-CYoMK+44s/E@public.gmane.org>
Cc: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
	Stephen Warren <swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Subject: Re: [PATCH V3] dtc: Add ability to delete nodes and properties
Date: Thu, 06 Sep 2012 09:58:33 -0600	[thread overview]
Message-ID: <5048C829.30802@wwwdotorg.org> (raw)
In-Reply-To: <E1T9bae-0001JH-EF-CYoMK+44s/E@public.gmane.org>

On 09/06/2012 06:53 AM, Jon Loeliger wrote:
>> On Tue, Aug 07, 2012 at 10:50:15PM -0600, Stephen Warren wrote:
>>> dtc currently allows the contents of properties to be changed, and the
>>> contents of nodes to be added to. There are situations where removing
>>> properties or nodes may be useful. This change implements the following
>>> syntax to do that:
>>>
>>>     / {
>>>         /delete-property/ propname;
>>>         /delete-node/ nodename;
>>>     };
>>>
>>> or:
>>>
>>>     /delete-node/ &noderef;
...
>> Acked-by: David Gibson <david-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@public.gmane.org>
> 
> Applied!

Thanks very much!

Any further thoughts on named constants and whether my gpp-integration
hack should be pursued?

      parent reply	other threads:[~2012-09-06 15:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-08  4:50 [PATCH V3] dtc: Add ability to delete nodes and properties Stephen Warren
     [not found] ` <1344401415-3214-1-git-send-email-swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-08-22  4:12   ` Stephen Warren
2012-09-04  0:05   ` David Gibson
     [not found]     ` <20120904000539.GH8526-W9XWwYn+TF0XU02nzanrWNbf9cGiqdzd@public.gmane.org>
2012-09-06 12:53       ` Jon Loeliger
     [not found]         ` <E1T9bae-0001JH-EF-CYoMK+44s/E@public.gmane.org>
2012-09-06 15:58           ` Stephen Warren [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=5048C829.30802@wwwdotorg.org \
    --to=swarren-3lzwwm7+weoh9zmkesr00q@public.gmane.org \
    --cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
    --cc=jdl-CYoMK+44s/E@public.gmane.org \
    --cc=swarren-DDmLM1+adcrQT0dZR+AlfA@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;
as well as URLs for NNTP newsgroup(s).