From: Krzysztof Kozlowski <krzk@kernel.org>
To: John Madieu <john.madieu.xa@bp.renesas.com>,
prabhakar.mahadev-lad.rj@bp.renesas.com, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, geert+renesas@glider.be
Cc: biju.das.jz@bp.renesas.com, claudiu.beznea@tuxon.dev,
linux@armlinux.org.uk, magnus.damm@gmail.com,
mcoquelin.stm32@gmail.com, alexandre.torgue@foss.st.com,
netdev@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH net-next 0/3] net: stmmac: add physical port identification support
Date: Thu, 4 Dec 2025 17:55:19 +0100 [thread overview]
Message-ID: <f169f89b-3694-41b0-a431-cc845ad659da@kernel.org> (raw)
In-Reply-To: <20251204164028.7321-1-john.madieu.xa@bp.renesas.com>
On 04/12/2025 17:40, John Madieu wrote:
> This series adds physical port identification support to the stmmac driver,
> enabling userspace to query hardware-stable identifiers for network interfaces
> via ndo_get_phys_port_id() and ndo_get_phys_port_name().
>
> On systems with multiple ethernet controllers sharing the same driver,
> physical port identification provides stable identifiers that persist
> across reboots and are independent of interface enumeration order.
> This is particularly useful for predictable network interface naming
> and for correlating interfaces with physical connectors.
>
> The implementation follows a two-tier approach:
>
Please slow down. You sent three copies of the same.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-12-04 16:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-04 16:40 [PATCH net-next 0/3] net: stmmac: add physical port identification support John Madieu
2025-12-04 16:40 ` [PATCH net-next 1/3] " John Madieu
2025-12-04 16:40 ` [PATCH net-next 2/3] dt-bindings: net: renesas-gbeth: Add port-id property John Madieu
2025-12-09 20:34 ` Rob Herring
2025-12-04 16:40 ` [PATCH net-next 3/3] net: stmmac: dwmac-renesas-gbeth: add physical port identification John Madieu
2025-12-04 16:55 ` Krzysztof Kozlowski [this message]
2025-12-04 17:02 ` [PATCH net-next 0/3] net: stmmac: add physical port identification support John Madieu
2025-12-04 17:09 ` Russell King (Oracle)
-- strict thread matches above, loose matches on Subject: below --
2025-12-04 16:37 John Madieu
2025-12-04 17:07 ` Russell King (Oracle)
2025-12-04 17:09 ` John Madieu
2025-12-04 21:07 ` Andrew Lunn
2025-12-04 16:31 John Madieu
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=f169f89b-3694-41b0-a431-cc845ad659da@kernel.org \
--to=krzk@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=andrew+netdev@lunn.ch \
--cc=biju.das.jz@bp.renesas.com \
--cc=claudiu.beznea@tuxon.dev \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=geert+renesas@glider.be \
--cc=john.madieu.xa@bp.renesas.com \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=magnus.damm@gmail.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=robh@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;
as well as URLs for NNTP newsgroup(s).