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 08/74] livetree: Improve get_node_by_phandle()
Date: Wed, 28 Oct 2026 13:41:14 +1100 [thread overview]
Message-ID: <auFgv_f0av-JxMjg@gractus.seuss> (raw)
In-Reply-To: <20261026125615.055e7214@bootlin.com>
[-- Attachment #1: Type: text/plain, Size: 13696 bytes --]
On Mon, Oct 26, 2026 at 12:56:15PM +0100, Herve Codina wrote:
> Hi David,
>
> On Mon, 26 Oct 2026 12:33:51 +1100
> David Gibson <david@gibson.dropbear.id.au> wrote:
>
> > On Fri, Oct 23, 2026 at 06:15:33PM +0200, Herve Codina wrote:
> > > Hi David,
> > >
> > > On Fri, 23 Oct 2026 14:25:29 +1100
> > > David Gibson <david@gibson.dropbear.id.au> wrote:
> > >
> > > > On Wed, Aug 26, 2026 at 11:48:37AM +0200, Herve Codina wrote:
> > > > > get_node_by_phandle() allows to get a node based on its phandle value.
> > > > > It checks the phandle value against value available in internal node
> > > > > structure.
> > > > >
> > > > > This internal phandle value is updated during process_check() and so,
> > > > > get_node_by_phandle() cannot give correct results before the
> > > > > process_check() call.
> > > > >
> > > > > Improve get_node_by_phandle() to look at node phandle properties when
> > > > > the internal phandle value is not valid.
> > > > >
> > > > > This allows to return a correct matching node even if process_check()
> > > > > was not called yet.
> > > >
> > > > The idea is sound - it's always been kind of clunky that we need the
> > > > process_checks() pass to fill the phandles before we can use them.
> > > > But, there's at least one significant catch:
> > > >
> > > > [Aside: you might notice the way it's done violates the principle I
> > > > stated elsewhere of avoiding structures where you must know where you
> > > > are in the flow to know which parts are populated. My type
> > > > discipline has improved since I first wrote this code :)]
> > > >
> > > > We need to gracefully handle the case of malformed phandle /
> > > > linux,phandle properties; that's actually the reason for the weird
> > > > placement of this in checks.c. By treating it as a "check" we handle
> > > > this case by failing the check. Other checks that rely on phandles
> > > > then have the 'explicit_phandles' check as a prereq so they don't need
> > > > to verify this again. We can still report errors for other checks
> > > > that don't rely on that (which is the whole point of the checks
> > > > mechanism).
> > > >
> > > > That's not the only way to do it, of course, but we need something to
> > > > check for that error case. Further notes on the code.
> > > >
> > > > > With the recently introduced FDT_PROPDATA_HANDLE dtb tag, this will be
> > > > > needed to update internal phandle references before the call to
> > > > > process_check(). Indeed, this tag allows to identify phandles and
> > > > > internal references need to be updated based on the phandle value before
> > > > > the process_check() call.
> > > > >
> > > > > Signed-off-by: Herve Codina <herve.codina@bootlin.com>
> > > > > ---
> > > > > livetree.c | 21 ++++++++++++++++++++-
> > > > > 1 file changed, 20 insertions(+), 1 deletion(-)
> > > > >
> > > > > diff --git a/livetree.c b/livetree.c
> > > > > index abe73de1..a9f8c5d2 100644
> > > > > --- a/livetree.c
> > > > > +++ b/livetree.c
> > > > > @@ -628,16 +628,35 @@ struct node *get_node_by_label(struct node *tree, const char *label)
> > > > > return NULL;
> > > > > }
> > > > >
> > > > > +static cell_t get_node_phandle_existing(struct node *node)
> > > > > +{
> > > > > + struct property *prop;
> > > > > +
> > > > > + if (phandle_is_valid(node->phandle))
> > > > > + return node->phandle;
> > > > > +
> > > > > + prop = get_property(node, "phandle");
> > > > > + if (!prop) {
> > > > > + prop = get_property(node, "linux,phandle");
> > > > > + if (!prop)
> > > > > + return 0;
> > > > > + }
> > > > > +
> > > > > + return propval_cell(prop);
> > > >
> > > > In the case of a malformed property, this could SEGV.
> > >
> > > Ok, will update to
> > > --- 8< ---
> > > if (prop->val.len != sizeof(cell_t))
> > > return 0;
> > >
> > > return propval_cell(prop)
> > > --- 8< ---
> > >
> > > >
> > > > > +}
> > > > > +
> > > > > struct node *get_node_by_phandle(struct node *tree, cell_t phandle)
> > > > > {
> > > > > struct node *child, *node;
> > > > > + cell_t tree_phandle;
> > > > >
> > > > > if (!phandle_is_valid(phandle)) {
> > > > > assert(generate_fixups);
> > > > > return NULL;
> > > > > }
> > > > >
> > > > > - if (tree->phandle == phandle) {
> > > > > + tree_phandle = get_node_phandle_existing(tree);
> > > >
> > > > This means that every time we search for a phandle, for every node
> > > > scanned before the destination with no phandle, we do a full property
> > > > scan to check that no, it still doesn't have a phandle.
> > > >
> > > > I don't care that much about dtc performance, but that's still a bit
> > > > much to swallow. I think we need to cache negative lookups to avoid
> > > > that. Happily, since there are two invalid phandle values this
> > > > shouldn't be too hard. We could, say, use tree->phandle == 0 to mean
> > > > we don't know if there's a phandle, and tree->phandle == -1 to mean
> > > > we've scanned the properties and we know there isn't one.
> > > >
> > > > In fact, caching property lookups might be the better way to do this.
> > > > Rather than having an explicit pass where tree->phandle is populated,
> > > > we could have get_node_by_phandle() cache its property scan (success
> > > > or failure) in tree->phandle.
> > > >
> > > > I think that's a more elegant approach than the current one, but we do
> > > > still need to handle the malformed property case.
> > >
> > > Well, get_node_phandle_existing() can be improved:
> > > ---- 8< ----
> > > static cell_t get_node_phandle_existing(struct node *node)
> > > {
> > > cell_t phandle1, phandle2;
> > > struct property *prop1, *prop2;
> > >
> > > if (phandle_is_valid(node->phandle))
> > > return node->phandle;
> > > if (node->phandle == ~0UL) {
> > > /*
> > > * We've already looked at existing properties and no valid
> > > * phandle value were present. Avoid looking at them again
> > > * and just return the invalid phandle value.
> > > */
> > > return 0;
> > > }
> > >
> > > /* Try to get it from the 'phandle' property */
> > > phandle1 = 0; /* Assume invalid */
> > > prop1 = get_property(node, "phandle");
> > > if (prop1) {
> > > if (prop1->val.len == sizeof(cell_t))
> > > phandle1 = propval_cell(prop1); /* Well formed -> Get it */
> > > }
> > >
> > > /* Try to get it from the 'linux,phandle' property */
> > > phandle2 = 0; /* Assume invalid */
> > > prop2 = get_property(node, "linux,phandle");
> > > if (prop2) {
> > > if (prop2->val.len == sizeof(cell_t))
> > > phandle2 = propval_cell(prop2); /* Well formed -> Get it */
> > > }
> > >
> > > if (prop1 && prop2) {
> > > /*
> > > * Both property are present. They values must be the same
> > > * and valid.
> > > */
> > > if (phandle1 == phandle2) && phandle_is_valid(phandle1)) {
> > > /* Ok, Cache this correct phandle value and return it */
> > > node->phandle = phandle1;
> > > return phandle1;
> > > }
> > > } else if (prop1) {
> > > /*
> > > * Only the 'phandle' property is present.
> > > * Check its value validity
> > > */
> > > if (phandle_is_valid(phandle1)) {
> > > /* Ok, Cache this correct phandle value and return it */
> > > node->phandle = phandle1;
> > > return phandle1;
> > > }
> > > } else if (prop2) {
> > > /*
> > > * Only the 'linux,phandle' property is present.
> > > * Check its value validity
> > > */
> > > if (phandle_is_valid(phandle2)) {
> > > /* Ok, Cache this correct phandle value and return it */
> > > node->phandle = phandle2;
> > > return phandle2;
> > > }
> > > }
> > >
> > > /*
> > > * No valid phandle value were found. Cache this information and return
> > > * the invalid phandle value.
> > > */
> > > node->phandle == ~0UL;
> > > return 0;
> > > }
> > > --- 8< ---
> >
> > That looks good to me. But the "existing" in the name no longer says
> > anything useful - this can be the standard way to get a node's
> > phandle. In fact it might be worth changing the name of the
> > node->phandle field to make sure we don't have any stale users rather
> > than going through the get_phandle() function.
>
> Ok, I will rename node->phandle to node->phandle_ and add a comment saying
> that phandle_ field must not be accessed directly.
You can even switch it back after you've checked there are no stray
accesses to it.
> Related to existing users, I can see check_explicit_phandles() available
> in the checks.c file.
>
> check_explicit_phandles() could use the new get_node_phandle_exising() with
> the caching feature. The only problematic part will be
> --- 8< ---
> if (linux_phandle && phandle && (phandle != linux_phandle))
> FAIL(c, dti, node, "mismatching 'phandle' and 'linux,phandle'"
> " properties");
> --- 8< ---
>
> Indeed, this check is done in get_node_phandle_existing() and the function
> returns 0 (invalid phandle) when both properties are set with a different
> value. A value other than 0 should be returned by get_node_phandle_existing()
> to identify that mismatching properties values.
>
> This should not be a big deal if we introduced a new invalid phandle value:
> - 0:
> Invalid value. Can be returned by get_node_phandle_existing().
>
> - ~0:
> Unresolved value (phandle value in properties) or value cached in
> phandle->node_ for "mismatch 'phandle' and 'linux,phandle' properties
> values". Can be returned by get_node_phandle_existing().
>
> - (~0)-1:
> Invalid value in properties and or value cached in phandle->node_ for Invalid value.
> Will not be returned by get_node_phandle_existing().
> When this cached value is found, 0 will be returned.
>
> In phandle_is_valid(), those 3 values will be checked to determine if the phandle
> value is valid or not.
Alas, we can't do that. Which phandle values are valid is long
established from the IEEE1275 days, and we can't really change it. I
don't _know_ if there are existing trees out there using 0xfffffffe as
a valid phandle, but there could be.
*thinks*
In some ways it would be elegant for get_node_phandle_existing() to
report the various different error conditions separately, but I think
the awkwardness of passing that information back to the checks is
going to outweigh it.
So, I think we're actually better off separating lookup of phandles
from validation. So get_node_phandle_existing() (or whatever we call
it) will return 0 if there's no valid phandle, whether that's simply
because it's missing, or there's something malformed. Separately
check_explicit_phandles() will report specific types of malformed
phandle properties.
It does result in a little redudant logic, but I think it's the best
overall approach for now.
> Now last point, renaming get_node_phandle_existing().
>
> get_node_phandle() already exist. It get a phandle but also if the node doesn't
> have a phandle, it allocate a new phandle value and set node "phandle" or
> "linux, phandle" property to this allocated value.
Ah, sorry, I misunderstood what the "existing" was referring to.
> IHMO, get_node_phandle() should be renamed to set_node_phandle() and
> get_node_phandle_existing() should be renamed to get_node_phandle().
Right, the existing name is bad. But let's go with
get_or_assign_phandle() for the existing one and get_phandle() for the
new one. (The "node" added no useful information and this way they're
two new names to reduce confusion).
> Does all of these make sense?
>
> I so, I will try to implement that and maybe I will see other issue I might
> have missed.
>
> Worth noting that if you're ok to rename get_node_phandle() to
> set_node_phandle(), I will do it in a dedicated patch. Indeed, this will
> ensure that get_node_phandle() has been renamed everywhere (compilation
> without failure) and so I can safely rename get_node_phandle_existing() to
> get_node_phandle() in a next patch.
>
> >
> > > In get_node_by_phandle(), no change compared to my proposition and so the
> > > full function is:
> > > --- 8< ---
> > > struct node *get_node_by_phandle(struct node *tree, cell_t phandle)
> > > {
> > > struct node *child, *node;
> > > cell_t tree_phandle;
> > >
> > > if (!phandle_is_valid(phandle)) {
> > > assert(generate_fixups);
> > > return NULL;
> > > }
> > >
> > > tree_phandle = get_node_phandle_existing(tree);
> > > if (phandle_is_valid(tree_phandle) && tree_phandle == phandle) {
> > > if (tree->deleted)
> > > return NULL;
> > > return tree;
> > > }
> > >
> > > for_each_child(tree, child) {
> > > node = get_node_by_phandle(child, phandle);
> > > if (node)
> > > return node;
> > > }
> > >
> > > return NULL;
> > > }
> > > --- 8< ---
> > >
> > > Caching should work correctly without any other modification.
> > >
> > > I let you double-check on your side. Let me know about your opinion.
> >
> > Yes, I think that should work.
> >
>
> Best regards,
> Hervé
>
--
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 --]
next prev parent reply other threads:[~2026-10-28 2:41 UTC|newest]
Thread overview: 101+ 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
2026-10-19 13:56 ` Herve Codina
2026-10-20 6:41 ` David Gibson
2026-10-20 11:14 ` Herve Codina
2026-10-21 1:44 ` David Gibson
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-10-21 3:13 ` David Gibson
2026-10-21 17:26 ` Herve Codina
2026-10-22 3:02 ` David Gibson
2026-10-22 9:47 ` Herve Codina
2026-10-23 1:23 ` David Gibson
2026-10-23 11:29 ` Herve Codina
2026-10-26 1:30 ` David Gibson
2026-10-26 13:18 ` Herve Codina
2026-08-26 9:48 ` [RFC PATCH v2 08/74] livetree: Improve get_node_by_phandle() Herve Codina
2026-10-23 3:25 ` David Gibson
2026-10-23 16:15 ` Herve Codina
2026-10-26 1:33 ` David Gibson
2026-10-26 11:56 ` Herve Codina
2026-10-28 2:41 ` David Gibson [this message]
2026-10-28 8:41 ` 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=auFgv_f0av-JxMjg@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®