All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Simon Glass <sjg@chromium.org>
Cc: Devicetree Compiler <devicetree-compiler@vger.kernel.org>
Subject: Re: [PATCH 0/5] fdtput: Make it clearer how to create nodes
Date: Wed, 28 Oct 2026 12:58:56 +1100	[thread overview]
Message-ID: <auFWwlb3Wbun6WR0@gractus.seuss> (raw)
In-Reply-To: <20261027120126.2613353-1-sjg@chromium.org>

[-- Attachment #1: Type: text/plain, Size: 1709 bytes --]

On Tue, Oct 27, 2026 at 06:01:14AM -0600, Simon Glass wrote:
> fdtput can create nodes with -c, and -p creates any missing nodes along
> the way, but this is easy to miss. A user has asked for a way to add
> nodes, not realising that one exists.
> 
> The first patch explains in the help and the manual how to create
> nodes. The second fixes -p for a path which starts with an alias, which
> creates a stray node at the top level. The third suggests -p when a
> node is missing, naming the parent which is missing. The fourth names
> the property, rather than the node, when it cannot be deleted. The
> fifth corrects the manual's description of -t.
> 
> Link: https://github.com/dgibson/dtc/issues/49

I've merged patches 1 & 5.  I think 2 & 4 need some refinement.  3
looks good to me, but I haven't merged since it may depend on 2.

> 
> 
> Simon Glass (5):
>   fdtput: Explain how to create nodes
>   fdtput: Follow an alias when creating nodes with -p
>   fdtput: Suggest -p when a node is missing
>   fdtput: Name the property when it cannot be deleted
>   fdtput: Correct the description of -t in the manual
> 
>  Documentation/manual.txt | 38 ++++++++++++++++++++++++++++++-----
>  fdtput.c                 | 43 ++++++++++++++++++++++++++++++++++------
>  tests/run_tests.sh       | 11 ++++++++++
>  3 files changed, 81 insertions(+), 11 deletions(-)
> 
> ---
> base-commit: 9a712e0c7fb7eec14cc83a06d7a2ff7910f49b97
> branch: fdtput-nodes
> 
> -- 
> 2.43.0
> 
> 

-- 
David Gibson (he or they)	| 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

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      parent reply	other threads:[~2026-10-28  1:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-27 12:01 [PATCH 0/5] fdtput: Make it clearer how to create nodes Simon Glass
2026-10-27 12:01 ` [PATCH 1/5] fdtput: Explain " Simon Glass
2026-10-27 12:01 ` [PATCH 2/5] fdtput: Follow an alias when creating nodes with -p Simon Glass
2026-10-28  1:34   ` David Gibson
2026-10-27 12:01 ` [PATCH 3/5] fdtput: Suggest -p when a node is missing Simon Glass
2026-10-28  1:39   ` David Gibson
2026-10-28  7:39     ` Simon Glass
2026-10-27 12:01 ` [PATCH 4/5] fdtput: Name the property when it cannot be deleted Simon Glass
2026-10-28  1:43   ` David Gibson
2026-10-27 12:01 ` [PATCH 5/5] fdtput: Correct the description of -t in the manual Simon Glass
2026-10-28  1:58 ` David Gibson [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=auFWwlb3Wbun6WR0@gractus.seuss \
    --to=david@gibson.dropbear.id.au \
    --cc=devicetree-compiler@vger.kernel.org \
    --cc=sjg@chromium.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.