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, alexander.stein@ew.tq-group.com,
aziz.sellami@nxp.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, imx@lists.linux.dev
Subject: Re: [PATCH v2 0/2] net: enetc: fix fallback PHY address handling and do not skip setting for addr 0
Date: Tue, 10 Mar 2026 10:00:08 +0000 [thread overview]
Message-ID: <177313680829.2167779.1393804264443460774.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260305031211.904812-1-wei.fang@nxp.com>
Hello:
This series was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Thu, 5 Mar 2026 11:12:09 +0800 you wrote:
> There are two potential issues when PHY address 0 is used on the board,
> see the commit messages of the patches for more details.
>
> ---
> v2:
> 1. No functional changes, only split the v1 patch into two patches.
> 2. Collect tags.
> v1 link: https://lore.kernel.org/imx/20260303103047.228005-1-wei.fang@nxp.com/
>
> [...]
Here is the summary with links:
- [v2,1/2] net: enetc: fix incorrect fallback PHY address handling
https://git.kernel.org/netdev/net/c/246953f33e8c
- [v2,2/2] net: enetc: do not skip setting LaBCR[MDIO_PHYAD_PRTAD] for addr 0
https://git.kernel.org/netdev/net/c/dbe17e7783cb
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:[~2026-03-10 10:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-05 3:12 [PATCH v2 0/2] net: enetc: fix fallback PHY address handling and do not skip setting for addr 0 Wei Fang
2026-03-05 3:12 ` [PATCH v2 1/2] net: enetc: fix incorrect fallback PHY address handling Wei Fang
2026-03-05 3:12 ` [PATCH v2 2/2] net: enetc: do not skip setting LaBCR[MDIO_PHYAD_PRTAD] for addr 0 Wei Fang
2026-03-10 10: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=177313680829.2167779.1393804264443460774.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexander.stein@ew.tq-group.com \
--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