mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Herve Codina <herve.codina@bootlin.com>
Cc: Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	David Lechner <dlechner@baylibre.com>,
	Ayush Singh <ayush@beagleboard.org>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	devicetree-compiler@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, devicetree-spec@vger.kernel.org,
	Hui Pu <hui.pu@gehealthcare.com>,
	Ian Ray <ian.ray@gehealthcare.com>,
	Luca Ceresoli <luca.ceresoli@bootlin.com>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [RFC PATCH v2 05/74] libfdt: Prepare for metadata tag support
Date: Mon, 19 Oct 2026 11:58:17 +1100	[thread overview]
Message-ID: <atVrHkfXl10FTEye@gractus.seuss> (raw)
In-Reply-To: <20260826094950.1088288-6-herve.codina@bootlin.com>

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

On Wed, Aug 26, 2026 at 11:48:34AM +0200, Herve Codina wrote:
> Metadata tags are tags carrying extra information, either global to
> the DTB, specific to a node, or specific to a property.
> 
> In several places (e.g. node/property iterators), these tags just need
> to be skipped. Introduce fdt_next_tag_filter() which wraps
> fdt_next_tag() and uses a user-supplied filter function to decide
> whether a tag should be hidden from the caller. Filtered-out tags are
> returned as FDT_NOP.
> 
> Introduce fdt_tag_filter_skip_metadata() a filter function whose purpose
> is to filter metadata tags; actual metadata tag filtering will be added
> when metadata tags are defined.
> 
> Metadata tags must also be handled when a DTB is modified. They have to
> be removed or skipped depending on the modification.
> 
> Here also, introduce fdt_tag_is_property_metadata() to provide a central
> check for whether a tag is a property metadata tag; actual metadata
> check will be added when metadata tags are defined.
> 
> Signed-off-by: Herve Codina <herve.codina@bootlin.com>
> ---
>  libfdt/fdt.c             | 34 +++++++++++++--
>  libfdt/fdt_ro.c          |  3 +-
>  libfdt/fdt_rw.c          | 90 +++++++++++++++++++++++++++++++++-------
>  libfdt/fdt_wip.c         | 23 +++++++++-
>  libfdt/libfdt_internal.h | 10 +++++
>  5 files changed, 140 insertions(+), 20 deletions(-)
> 
> diff --git a/libfdt/fdt.c b/libfdt/fdt.c
> index 7941632f..8c026f26 100644
> --- a/libfdt/fdt.c
> +++ b/libfdt/fdt.c
> @@ -323,6 +323,33 @@ uint32_t fdt_next_tag(const void *fdt, int startoffset, int *nextoffset)
>  	return fdt_next_tag_(fdt, startoffset, nextoffset, NULL);
>  }
>  
> +uint32_t fdt_next_tag_filter(const void *fdt, int offset, int *nextoffset,
> +			     bool (*tag_filter)(void *priv, uint32_t tag),
> +			     void *priv)

I don't really see why a higher order function is more useful than
skipping tags you don't care about from the caller.

> +{
> +	int startoffset = offset;
> +	uint32_t tag;
> +
> +	tag = fdt_next_tag_(fdt, startoffset, nextoffset, NULL);
> +	if (tag == FDT_END)
> +		return tag;
> +
> +	if (tag_filter(priv, tag))
> +		return FDT_NOP;
> +
> +	return tag;
> +}
> +
> +bool fdt_tag_filter_skip_metadata(void *data, uint32_t tag)
> +{
> +	return false;
> +}
> +
> +bool fdt_tag_is_property_metadata(uint32_t tag)
> +{
> +	return false;
> +}
> +
>  int fdt_check_node_offset_(const void *fdt, int offset)
>  {
>  	if (!can_assume(VALID_INPUT)
> @@ -355,7 +382,8 @@ int fdt_root_offset(const void *fdt)
>  
>  	do {
>  		offset = nextoffset;
> -		tag = fdt_next_tag(fdt, offset, &nextoffset);
> +		tag = fdt_next_tag_filter(fdt, offset, &nextoffset,
> +					  fdt_tag_filter_skip_metadata, NULL);
>  		switch (tag) {
>  		case FDT_END_NODE:
>  		case FDT_PROP:
> @@ -393,8 +421,8 @@ int fdt_next_node(const void *fdt, int offset, int *depth)
>  
>  	do {
>  		offset = nextoffset;
> -		tag = fdt_next_tag(fdt, offset, &nextoffset);
> -
> +		tag = fdt_next_tag_filter(fdt, offset, &nextoffset,
> +					  fdt_tag_filter_skip_metadata, NULL);
>  		switch (tag) {
>  		case FDT_PROP:
>  		case FDT_NOP:
> diff --git a/libfdt/fdt_ro.c b/libfdt/fdt_ro.c
> index 50c0a8bc..ea6a540d 100644
> --- a/libfdt/fdt_ro.c
> +++ b/libfdt/fdt_ro.c
> @@ -206,7 +206,8 @@ static int nextprop_(const void *fdt, int offset)
>  	int nextoffset;
>  
>  	do {
> -		tag = fdt_next_tag(fdt, offset, &nextoffset);
> +		tag = fdt_next_tag_filter(fdt, offset, &nextoffset,
> +					  fdt_tag_filter_skip_metadata, NULL);
>  
>  		switch (tag) {
>  		case FDT_END:
> diff --git a/libfdt/fdt_rw.c b/libfdt/fdt_rw.c
> index 1c6ce0a3..30f3da40 100644
> --- a/libfdt/fdt_rw.c
> +++ b/libfdt/fdt_rw.c
> @@ -259,6 +259,42 @@ int fdt_prop_remove_unknown_tags(void *fdt, bool force_inplace,
>  	return 0;
>  }
>  
> +int fdt_prop_remove_metadata_tags(void *fdt, bool force_inplace,
> +				  int prop_offset)
> +{
> +	int nextoffset, offset;
> +	uint32_t tag;
> +
> +	/*
> +	 * Only inplace using nopify is supported even if we could use an other
> +	 * method involving splices if force_inplace is set to false.
> +	 */

As with earlier things, I'd really prefer to see this splice, based on
principle of least surprise.

> +
> +	tag = fdt_next_tag(fdt, prop_offset, &nextoffset);
> +	if (tag == FDT_END)
> +		return nextoffset;
> +
> +	/*
> +	 * Look at all tags related to the current property. I.e. tags after the
> +	 * current property and before either the next property, a sub-node  or
> +	 * the end of current node
> +	 */
> +	do {
> +		offset = nextoffset;
> +		tag = fdt_next_tag(fdt, offset, &nextoffset);
> +		if (tag == FDT_END)
> +			return nextoffset;
> +
> +		/* Remove metadata tags related to the property */
> +		if (fdt_tag_is_property_metadata(tag))
> +			fdt_nopify_area(fdt, offset, nextoffset);

The distinction between "metadata" and other tags doesn't make much
sense to me.  Specifically why would the tag being "metadata" make it
more of a candidate for removal?  What we need to know (for the
callers so far) is whether the tag is invalidated by changing the
contents of the property: I can't see how that would be related to
whether it's "metadata" or not.

> +
> +	} while ((tag != FDT_PROP) && (tag != FDT_BEGIN_NODE) &&
> +		 (tag != FDT_END_NODE));
> +
> +	return 0;
> +}
> +
>  static int fdt_resize_property_(void *fdt, int nodeoffset,
>  				const char *name, int namelen,
>  				int len, struct fdt_property **prop)
> @@ -273,10 +309,18 @@ static int fdt_resize_property_(void *fdt, int nodeoffset,
>  		return oldlen;
>  
>  	/*
> -	 * The property is resized. Remove possible unknown tags related to the
> -	 * property downgrading the dtb version.
> +	 * The property is resized and data are going to be modified. Remove
> +	 * property metadata tags
>  	 */
>  	prop_offset = fdt_ptr_offset_(fdt, *prop);
> +	err = fdt_prop_remove_metadata_tags(fdt, false, prop_offset);
> +	if (err)
> +		return err;
> +
> +	/*
> +	 * Remove also possible unknown tags related to the property downgrading
> +	 * the dtb version.
> +	 */
>  	err = fdt_prop_remove_unknown_tags(fdt, false, prop_offset, true);
>  	if (err)
>  		return err;
> @@ -289,7 +333,7 @@ static int fdt_resize_property_(void *fdt, int nodeoffset,
>  	return 0;
>  }
>  
> -static int fdt_node_skip_unknown_tags(void *fdt, int next)
> +static int fdt_node_skip_unknown_and_metadata_tags(void *fdt, int next)
>  {
>  	int nextoffset = next;
>  	int offset;
> @@ -299,6 +343,7 @@ static int fdt_node_skip_unknown_tags(void *fdt, int next)
>  	 * Skip all tags related to the current node. I.e. tags after the
>  	 * current node and before either the next property, a sub-node or the
>  	 * end of current node.
> +	 * FDT_NOP, unknown tags and potential node metadata tags are skipped.
>  	 */
>  	do {
>  		offset = nextoffset;
> @@ -332,10 +377,10 @@ static int fdt_add_property_(void *fdt, int nodeoffset, const char *name,
>  
>  	/*
>  	 * nextoffset it at the first tag after the node.
> -	 * Skip possible unknown tags related to the node in order to add the
> -	 * property after those tags.
> +	 * Skip possible unknown tags and metadata tags related to the node in
> +	 * order to add the property after those tags.
>  	 */
> -	nextoffset = fdt_node_skip_unknown_tags(fdt, nextoffset);
> +	nextoffset = fdt_node_skip_unknown_and_metadata_tags(fdt, nextoffset);

This makes even less sense to me.  The tags following the node belong
to the node, until either FDT_BEGIN_NODE, FDT_END_NODE or FDT_PROP.
We need to skip all of them regardless of whether they're "metadata"
or not.

>  	if (nextoffset < 0)
>  		return nextoffset;
>  
> @@ -453,6 +498,12 @@ int fdt_appendprop(void *fdt, int nodeoffset, const char *name,
>  		if (err)
>  			return err;
>  
> +		/*
> +		 * We append data to the property. If known metadata tags are
> +		 * present, they are related to existing data and not impacted
> +		 * by data added. No need to remove them.

You don't know that.  It might be true for the tags you have in mind
so far, but there's no guarantee.  It's a contrived example, but a tag
which gives "number of 0 bytes in the property" would be invalidated
by an append, for example.

> +		 */
> +
>  		newlen = len + oldlen;
>  		err = fdt_splice_struct_(fdt, prop->data,
>  					 FDT_TAGALIGN(oldlen),
> @@ -484,11 +535,16 @@ int fdt_delprop(void *fdt, int nodeoffset, const char *name)
>  	if (!prop)
>  		return len;
>  
> +	/* The property is going to be removed. Remove its metadata tags */
> +	prop_offset = fdt_ptr_offset_(fdt, prop);
> +	err = fdt_prop_remove_metadata_tags(fdt, false, prop_offset);
> +	if (err)
> +		return err;

All tags from the property to the next END_NODE or FDT_PROP need to be
removed, regardless of whether they're "metadata" or not.

Also, rather than removing them one by one, I'd prefer to see the
total length of them calculated, and remove the property and extra
tags with a single splice.

> +
>  	/*
> -	 * The property is going to be removed. Remove also possible unknown
> -	 * tags related to this property. Keep the dtb version unchanged.
> +	 * Remove also possible unknown tags related to this property.
> +	 * Keep the dtb version unchanged.
>  	 */
> -	prop_offset = fdt_ptr_offset_(fdt, prop);
>  	err = fdt_prop_remove_unknown_tags(fdt, false, prop_offset, false);
>  	if (err)
>  		return err;
> @@ -522,10 +578,15 @@ int fdt_add_subnode_namelen(void *fdt, int parentoffset,
>  		return offset;
>  
>  	/*
> -	 * Try to place the new node after the parent's properties and unknown
> -	 * tags related to those properties.
> -	 * Unknown tags are reported as FDT_NOP tags by fdt_next_tag.
> -	 * Skipping FDT_NOP tags will correctly skip unknown tags.
> +	 * Try to place the new node after:
> +	 *  - the parent's properties
> +	 *  - the metadata tags related to those properties

Again, the "metadata" distinction doesn't really make sense.  You want
to place the new node immediately before the first FDT_BEGIN_NODE or
FDT_END_NODE tag within the parent node.

> +	 *  - unknown tags related to those properties.
> +	 * Unknown tags are reported as FDT_NOP tags by fdt_next_tag_filter.
> +	 * metadata tags are also reported as FDT_NOP by fdt_next_tag_filter
> +	 * thanks to the filter function used.
> +	 * Skipping FDT_NOP tags will correctly skip unknown tags and metadata
> +	 * tags.
>  	 */
>  	tag = fdt_next_tag(fdt, parentoffset, &nextoffset);
>  	/* the fdt_subnode_offset_namelen() should ensure this never hits */
> @@ -533,7 +594,8 @@ int fdt_add_subnode_namelen(void *fdt, int parentoffset,
>  		return -FDT_ERR_INTERNAL;
>  	do {
>  		offset = nextoffset;
> -		tag = fdt_next_tag(fdt, offset, &nextoffset);
> +		tag = fdt_next_tag_filter(fdt, offset, &nextoffset,
> +					  fdt_tag_filter_skip_metadata, NULL);
>  	} while ((tag == FDT_PROP) || (tag == FDT_NOP));
>  
>  	nh = fdt_offset_ptr_w_(fdt, offset);
> diff --git a/libfdt/fdt_wip.c b/libfdt/fdt_wip.c
> index 7ca3ffbc..b2f9f8d1 100644
> --- a/libfdt/fdt_wip.c
> +++ b/libfdt/fdt_wip.c
> @@ -31,6 +31,17 @@ int fdt_setprop_inplace_namelen_partial(void *fdt, int nodeoffset,
>  	if ((unsigned)proplen < (len + idx))
>  		return -FDT_ERR_NOSPACE;
>  
> +	if (idx < (unsigned)proplen) {
> +		/*
> +		 * The property existing data are going to be modified.
> +		 * The property metadata tags are related to the property
> +		 * data. Remove them.
> +		 */
> +		err = fdt_prop_remove_metadata_tags(fdt, true, prop_offset);
> +		if (err)
> +			return err;
> +	}

Similar to removal, I'd prefer to see a calculation of the total
length and a single splice_region, rather than removing them one by
one.


>  	/*
>  	 * Remove unknown tags related to the property downgrading the dtb
>  	 * version.
> @@ -81,10 +92,18 @@ int fdt_nop_property(void *fdt, int nodeoffset, const char *name)
>  		return len;
>  
>  	/*
> -	 * The property is going to be removed (nopified). Remove unknown tags
> -	 * related to this property. Keep the dtb version unchanged.
> +	 * The property is going to be removed (nopified). Remove its metadata
> +	 * tags
>  	 */
>  	prop_offset = fdt_ptr_offset_(fdt, prop);
> +	err = fdt_prop_remove_metadata_tags(fdt, true, prop_offset);
> +	if (err)
> +		return err;
> +
> +	/*
> +	 * Remove also possible unknown tags related to this property.
> +	 * Keep the dtb version unchanged.
> +	 */
>  	err = fdt_prop_remove_unknown_tags(fdt, true, prop_offset, false);
>  	if (err)
>  		return err;
> diff --git a/libfdt/libfdt_internal.h b/libfdt/libfdt_internal.h
> index d4154119..47dfc0d4 100644
> --- a/libfdt/libfdt_internal.h
> +++ b/libfdt/libfdt_internal.h
> @@ -23,6 +23,14 @@ int32_t fdt_ro_probe_(const void *fdt);
>  uint32_t fdt_next_tag_(const void *fdt, int startoffset, int *nextoffset,
>  		       bool *is_unknown);
>  
> +uint32_t fdt_next_tag_filter(const void *fdt, int offset, int *nextoffset,
> +			     bool (*tag_filter)(void *priv, uint32_t tag),
> +			     void *priv);
> +
> +bool fdt_tag_filter_skip_metadata(void *data, uint32_t tag);
> +
> +bool fdt_tag_is_property_metadata(uint32_t tag);
> +
>  int fdt_get_structured_tag_data(uint32_t tag, const void *fdt, int offset,
>  				uint32_t *data_len);
>  
> @@ -31,6 +39,8 @@ int fdt_check_prop_offset_(const void *fdt, int offset);
>  
>  int fdt_prop_remove_unknown_tags(void *fdt, bool force_inplace,
>  				 int prop_offset, bool downgrade_version);
> +int fdt_prop_remove_metadata_tags(void *fdt, bool force_inplace,
> +				  int prop_offset);
>  
>  int fdt_getprop_offset_namelen(const void *fdt, int nodeoffset,
>  			       const char *name, int namelen);
> -- 
> 2.55.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 --]

  reply	other threads:[~2026-10-19  0:58 UTC|newest]

Thread overview: 84+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-26  9:48 [RFC PATCH v2 00/74] Add support for dtb metadata and addon device-trees Herve Codina
2026-08-26  9:48 ` [RFC PATCH v2 01/74] dtc-parser.y: Avoid an empty proplist Herve Codina
2026-10-14  9:25   ` David Gibson
2026-08-26  9:48 ` [RFC PATCH v2 02/74] Introduce v20 dtb version Herve Codina
2026-10-16  8:29   ` David Gibson
2026-08-26  9:48 ` [RFC PATCH v2 03/74] fdtdump: Introduce get_structured_tag_data() Herve Codina
2026-10-16  8:30   ` David Gibson
2026-10-19 13:17     ` Herve Codina
2026-08-26  9:48 ` [RFC PATCH v2 04/74] libfdt: Introduce fdt_get_structured_tag_data() Herve Codina
2026-10-19  0:24   ` David Gibson
2026-10-19 13:18     ` Herve Codina
2026-08-26  9:48 ` [RFC PATCH v2 05/74] libfdt: Prepare for metadata tag support Herve Codina
2026-10-19  0:58   ` David Gibson [this message]
2026-10-19 13:56     ` Herve Codina
2026-08-26  9:48 ` [RFC PATCH v2 06/74] dtc: Move fill_fullpaths() into build_dt_info() Herve Codina
2026-10-19  2:12   ` David Gibson
2026-08-26  9:48 ` [RFC PATCH v2 07/74] Add support for FDT_PROPDATA_PHANDLE dtb tag Herve Codina
2026-08-26  9:48 ` [RFC PATCH v2 08/74] livetree: Improve get_node_by_phandle() Herve Codina
2026-08-26  9:48 ` [RFC PATCH v2 09/74] dtc: Complete REF_PHANDLE markers with ref strings and is_local flags Herve Codina
2026-08-26  9:48 ` [RFC PATCH v2 10/74] tests: Add basic metadata tests Herve Codina
2026-08-26  9:48 ` [RFC PATCH v2 11/74] Add support for FDT_PROPDATA_PHANDLE_REF dtb tag Herve Codina
2026-08-26  9:48 ` [RFC PATCH v2 12/74] tests: metadata: Add external phandle reference tests Herve Codina
2026-08-26  9:48 ` [RFC PATCH v2 13/74] Add support for /addon/ keyword Herve Codina
2026-08-26  9:48 ` [RFC PATCH v2 14/74] tests: Add a test related to addon dt_flags header value Herve Codina
2026-08-26  9:48 ` [RFC PATCH v2 15/74] tests: metadata: Add a basic addon test Herve Codina
2026-08-26  9:48 ` [RFC PATCH v2 16/74] dtc: Introduce export symbols Herve Codina
2026-08-26  9:48 ` [RFC PATCH v2 17/74] dtc: Add support for /export/ dts keyword parsing Herve Codina
2026-08-26  9:48 ` [RFC PATCH v2 18/74] checks: Handle export symbols in fixup_phandle_references() Herve Codina
2026-08-26  9:48 ` [RFC PATCH v2 19/74] dtc: Add export symbols (/export/ keyword) in generated dts file Herve Codina
2026-08-26  9:48 ` [RFC PATCH v2 20/74] dtc: Extend complete_references() to handle export symbols Herve Codina
2026-08-26  9:48 ` [RFC PATCH v2 21/74] Add support for FDT_EXPORT_SYM dtb tag Herve Codina
2026-08-26  9:48 ` [RFC PATCH v2 22/74] tests: metadata: Add export symbols with local references tests Herve Codina
2026-08-26  9:48 ` [RFC PATCH v2 23/74] dtc: Add support for export symbols sorting Herve Codina
2026-08-26  9:48 ` [RFC PATCH v2 24/74] tests: metadata: Add a test " Herve Codina
2026-08-26  9:48 ` [RFC PATCH v2 25/74] Add support for FDT_EXPORT_SYM_REF dtb tag Herve Codina
2026-08-26  9:48 ` [RFC PATCH v2 26/74] tests: metadata: Add export symbols with external references tests Herve Codina
2026-08-26  9:48 ` [RFC PATCH v2 27/74] dtc: Introduce import symbols Herve Codina
2026-08-26  9:48 ` [RFC PATCH v2 28/74] dtc-parser: Introduce last_header_flags Herve Codina
2026-08-26  9:48 ` [RFC PATCH v2 29/74] dtc: Add support for /import/ dts keyword parsing Herve Codina
2026-08-26  9:48 ` [RFC PATCH v2 30/74] dtc: Add import symbols (/import/ keyword) in generated dts file Herve Codina
2026-08-26  9:49 ` [RFC PATCH v2 31/74] Add support for FDT_IMPORT_SYM dtb tag Herve Codina
2026-08-26  9:49 ` [RFC PATCH v2 32/74] tests: metadata: Add import symbols tests Herve Codina
2026-08-26  9:49 ` [RFC PATCH v2 33/74] dtc: Add support for import symbols sorting Herve Codina
2026-08-26  9:49 ` [RFC PATCH v2 34/74] tests: metadata: Improve sort test to check " Herve Codina
2026-08-26  9:49 ` [RFC PATCH v2 35/74] checks: Get 'chosen' node using get_subnode() Herve Codina
2026-08-26  9:49 ` [RFC PATCH v2 36/74] dtc: Change get_node_by_path() signature to take dt_info Herve Codina
2026-08-26  9:49 ` [RFC PATCH v2 37/74] dtc: Change get_node_by_label() " Herve Codina
2026-08-26  9:49 ` [RFC PATCH v2 38/74] dtc: Change get_node_by_phandle() " Herve Codina
2026-08-26  9:49 ` [RFC PATCH v2 39/74] dtc: Change get_node_by_ref() " Herve Codina
2026-08-26  9:49 ` [RFC PATCH v2 40/74] dtc: Change get_node_phandle() " Herve Codina
2026-08-26  9:49 ` [RFC PATCH v2 41/74] dtc: Change get_property_by_label() " Herve Codina
2026-08-26  9:49 ` [RFC PATCH v2 42/74] dtc: Change get_marker_label() " Herve Codina
2026-08-26  9:49 ` [RFC PATCH v2 43/74] dtc: Change fill_fullpaths() " Herve Codina
2026-08-26  9:49 ` [RFC PATCH v2 44/74] dtc: Introduce orphan nodes Herve Codina
2026-08-26  9:49 ` [RFC PATCH v2 45/74] dtc: Handle orphan nodes in get_xxx_by_yyy() Herve Codina
2026-08-26  9:49 ` [RFC PATCH v2 46/74] dtc: Avoid NULL fullpath for nodes in orphan trees Herve Codina
2026-08-26  9:49 ` [RFC PATCH v2 47/74] dtc: Handle orphan nodes in complete_references() Herve Codina
2026-08-26  9:49 ` [RFC PATCH v2 48/74] checks: Perform checks for orphan nodes Herve Codina
2026-08-26  9:49 ` [RFC PATCH v2 49/74] dtc: Rename add_orphan_node() to plugin_add_orphan_node() Herve Codina
2026-08-26  9:49 ` [RFC PATCH v2 50/74] dtc: Add basic support for addon orphan nodes in dts Herve Codina
2026-08-26  9:49 ` [RFC PATCH v2 51/74] Add support for FDT_BEGIN_NODE_REF dtb tag Herve Codina
2026-08-26  9:49 ` [RFC PATCH v2 52/74] tests: metadata: Add basic test for addon orphan nodes Herve Codina
2026-08-26  9:49 ` [RFC PATCH v2 53/74] dtc: Add support for missing root node in addon device-tree Herve Codina
2026-08-26  9:49 ` [RFC PATCH v2 54/74] tests: metadata: Add a test for addon without root node Herve Codina
2026-08-26  9:49 ` [RFC PATCH v2 55/74] dtc: Allow parser_get_node_by_ref() to return an orphan node for merging purpose Herve Codina
2026-08-26  9:49 ` [RFC PATCH v2 56/74] tests: metadata: Add a test related to orphan node merging Herve Codina
2026-08-26  9:49 ` [RFC PATCH v2 57/74] dtc: Add support for orphan nodes sorting Herve Codina
2026-08-26  9:49 ` [RFC PATCH v2 58/74] tests: metadata: Improve sort test to check " Herve Codina
2026-08-26  9:49 ` [RFC PATCH v2 59/74] dtc: Add support for references by path involving orphan nodes Herve Codina
2026-08-26  9:49 ` [RFC PATCH v2 60/74] tests: metadata: Add a test " Herve Codina
2026-08-26  9:49 ` [RFC PATCH v2 61/74] dtc: Add support for namespace labels references Herve Codina
2026-08-26  9:49 ` [RFC PATCH v2 62/74] tests: metadata: Add a test " Herve Codina
2026-08-26  9:49 ` [RFC PATCH v2 63/74] libfdt: Add support for applying an addon on a base device-tree blob Herve Codina
2026-08-26  9:49 ` [RFC PATCH v2 64/74] Add fdtaddon tool to apply an addon Herve Codina
2026-08-26  9:49 ` [RFC PATCH v2 65/74] tests: Add a first basic test for fdtaddon Herve Codina
2026-08-26  9:49 ` [RFC PATCH v2 66/74] tests: fdtaddon: Add a basic test for addons using an orphan nodes Herve Codina
2026-08-26  9:49 ` [RFC PATCH v2 67/74] tests: fdtaddon: Add a basic test for addons with unresolved phandle references Herve Codina
2026-08-26  9:49 ` [RFC PATCH v2 68/74] tests: fdtaddon: Add a basic test for addons with references by path to orphan nodes Herve Codina
2026-08-26  9:49 ` [RFC PATCH v2 69/74] tests: fdtaddon: Add a test for addons with properties identical to existing ones Herve Codina
2026-08-26  9:49 ` [RFC PATCH v2 70/74] tests: fdtaddon: Add a test for addons using namespace label references Herve Codina
2026-08-26  9:49 ` [RFC PATCH v2 71/74] tests: fdtaddon: Add a test for using 'stacked' addons Herve Codina
2026-08-26  9:49 ` [RFC PATCH v2 72/74] tests: fdtaddon: Add a test using more realistic dts and dtsa Herve Codina
2026-08-26  9:49 ` [RFC PATCH v2 73/74] libfdt/fdt_addon.c: Add support for an external resolver Herve Codina
2026-08-26  9:49 ` [RFC PATCH v2 74/74] fdtaddon: Add a simple " Herve Codina

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=atVrHkfXl10FTEye@gractus.seuss \
    --to=david@gibson.dropbear.id.au \
    --cc=ayush@beagleboard.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree-compiler@vger.kernel.org \
    --cc=devicetree-spec@vger.kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=geert@linux-m68k.org \
    --cc=herve.codina@bootlin.com \
    --cc=hui.pu@gehealthcare.com \
    --cc=ian.ray@gehealthcare.com \
    --cc=krzk@kernel.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luca.ceresoli@bootlin.com \
    --cc=robh@kernel.org \
    --cc=thomas.petazzoni@bootlin.com \
    /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

all inboxes | Powered by JetHome®