From: patchwork-bot+netdevbpf@kernel.org
To: Wei Fang <wei.fang@nxp.com>
Cc: claudiu.manoil@nxp.com, vladimir.oltean@nxp.com,
xiaoning.wang@nxp.com, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, aziz.sellami@nxp.com, imx@lists.linux.dev,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 net-next 0/3] net: enetc: add port MDIO support for both i.MX94 and i.MX95
Date: Wed, 26 Nov 2025 03:00:21 +0000 [thread overview]
Message-ID: <176412602124.975105.6622601514745827189.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251119102557.1041881-1-wei.fang@nxp.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 19 Nov 2025 18:25:54 +0800 you wrote:
> The NETC IP has one external master MDIO interface (eMDIO) for managing
> external PHYs, all ENETC ports share this eMDIO. The EMDIO function and
> the ENETC port MDIO are the virtual ports of this eMDIO, ENETC can use
> these virtual ports to access their PHYs. The difference is that EMDIO
> function is a 'global port', it can access all the PHYs on the eMDIO, so
> it provides a means for different software modules to share a single set
> of MDIO signals to access their PHYs.
>
> [...]
Here is the summary with links:
- [v3,net-next,1/3] net: enetc: set the external PHY address in IERB for port MDIO usage
https://git.kernel.org/netdev/net-next/c/6633df05f3ad
- [v3,net-next,2/3] net: enetc: set external PHY address in IERB for i.MX94 ENETC
https://git.kernel.org/netdev/net-next/c/50bfd9c06f0f
- [v3,net-next,3/3] net: enetc: update the base address of port MDIO registers for ENETC v4
https://git.kernel.org/netdev/net-next/c/10ba23a7f6cc
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-11-26 3:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-19 10:25 [PATCH v3 net-next 0/3] net: enetc: add port MDIO support for both i.MX94 and i.MX95 Wei Fang
2025-11-19 10:25 ` [PATCH v3 net-next 1/3] net: enetc: set the external PHY address in IERB for port MDIO usage Wei Fang
2025-11-19 15:20 ` Claudiu Manoil
2026-02-27 13:41 ` Alexander Stein
2026-02-28 3:52 ` Wei Fang
2026-03-02 9:10 ` Alexander Stein
2026-03-02 9:24 ` Wei Fang
2026-03-02 11:01 ` Alexander Stein
2026-03-02 12:43 ` Wei Fang
2025-11-19 10:25 ` [PATCH v3 net-next 2/3] net: enetc: set external PHY address in IERB for i.MX94 ENETC Wei Fang
2025-11-19 15:20 ` Claudiu Manoil
2025-11-19 10:25 ` [PATCH v3 net-next 3/3] net: enetc: update the base address of port MDIO registers for ENETC v4 Wei Fang
2025-11-19 15:19 ` Claudiu Manoil
2025-11-25 10:05 ` Paolo Abeni
2025-11-25 16:19 ` Andrew Lunn
2025-11-26 3:00 ` patchwork-bot+netdevbpf [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=176412602124.975105.6622601514745827189.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=aziz.sellami@nxp.com \
--cc=claudiu.manoil@nxp.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=imx@lists.linux.dev \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=vladimir.oltean@nxp.com \
--cc=wei.fang@nxp.com \
--cc=xiaoning.wang@nxp.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