From: Herve Codina <herve.codina@bootlin.com>
To: "Abdurrahman Hussain" <abdurrahman@nexthop.ai>
Cc: "Rob Herring" <robh@kernel.org>,
"Saravana Kannan" <saravanak@kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 0/4] of: teach overlay code to keep /aliases in sync
Date: Thu, 20 Aug 2026 08:17:48 +0200 [thread overview]
Message-ID: <20260820081748.5fb0d97e@bootlin.com> (raw)
In-Reply-To: <DKT4J20H0F84.17L06ULMZXN4A@nexthop.ai>
Hi Abdurrahman,
On Wed, 19 Aug 2026 11:15:35 -0700
"Abdurrahman Hussain" <abdurrahman@nexthop.ai> wrote:
...
> This series is narrowly about overlay-declared /aliases never entering
> aliases_lookup, so of_alias_get_id() returns -ENODEV and alias-based id
> pinning falls back to auto-assignment. It reproduces with no mux involved
> and doesn't depend on your talk.
>
> In v4 I'll drop the "underlying cause" clause; I can keep [2] only as
> prior-art context or drop it entirely — whichever you'd prefer.
IMHO, the talk describing the DT overlay usage in the lan966x context
doesn't add any benefit in your use case.
I would drop it but if you prefer to keep it as a reference explaining the
lan966x use-case, no problem.
Do what you feel is best.
Best regards,
Hervé
prev parent reply other threads:[~2026-08-20 6:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-21 21:36 [PATCH v3 0/4] of: teach overlay code to keep /aliases in sync Abdurrahman Hussain
2026-07-21 21:36 ` [PATCH v3 1/4] of: incrementally update /aliases lookup on reconfig notifications Abdurrahman Hussain
2026-07-21 21:48 ` sashiko-bot
2026-07-21 21:36 ` [PATCH v3 2/4] of/overlay: look up absolute target-paths absolutely Abdurrahman Hussain
2026-07-21 21:36 ` [PATCH v3 3/4] of/overlay: rewrite /aliases path values to live-tree paths Abdurrahman Hussain
2026-07-21 21:52 ` sashiko-bot
2026-07-21 21:36 ` [PATCH v3 4/4] of: unittest: cover /aliases updates from overlay apply/revert Abdurrahman Hussain
2026-07-21 21:46 ` sashiko-bot
2026-08-19 11:49 ` [PATCH v3 0/4] of: teach overlay code to keep /aliases in sync Herve Codina
2026-08-19 18:15 ` Abdurrahman Hussain
2026-08-20 6:17 ` Herve Codina [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=20260820081748.5fb0d97e@bootlin.com \
--to=herve.codina@bootlin.com \
--cc=abdurrahman@nexthop.ai \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=saravanak@kernel.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