From: Stephen Warren <swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Cc: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
Subject: Re: [PATCH V3] dtc: Add ability to delete nodes and properties
Date: Tue, 21 Aug 2012 22:12:58 -0600 [thread overview]
Message-ID: <50345C4A.50704@nvidia.com> (raw)
In-Reply-To: <1344401415-3214-1-git-send-email-swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
On 08/07/2012 10:50 PM, Stephen Warren wrote:
> From: Stephen Warren <swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
>
> 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;
David, does this look OK? I believe I've addresses the issues you
requested in order to give your ack. Thanks.
> ---
> v3:
> * Switch syntax from "propname /delprop/" to "/delete-property/ propname".
> Similar for /delete-node/.
> * Modify for_each_label() to skip deleted labels, and introduce
> for_each_label_withdel() for the case where we do want to include deleted
> labels in the iteration. Similar for properties and children.
next prev parent reply other threads:[~2012-08-22 4:12 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 [this message]
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
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=50345C4A.50704@nvidia.com \
--to=swarren-ddmlm1+adcrqt0dzr+alfa@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.