From: patchwork-bot+netdevbpf@kernel.org
To: luoxuanqiang <xuanqiang.luo@linux.dev>
Cc: netdev@vger.kernel.org, andrew@lunn.ch,
maxime.chevallier@bootlin.com, kuba@kernel.org,
hkallweit1@gmail.com, chleroy@kernel.org,
qingfang.deng@siflower.com.cn, hao.guan@siflower.com.cn,
linux@armlinux.org.uk, davem@davemloft.net, edumazet@google.com,
pabeni@redhat.com, linux-kernel@vger.kernel.org,
luoxuanqiang@kylinos.cn
Subject: Re: [PATCH net v5 0/6] net: phy: fix cleanup after probe failure
Date: Mon, 31 Aug 2026 00:30:16 +0000 [thread overview]
Message-ID: <178813621634.3966634.2247622864690119590.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260823035600.188864-1-xuanqiang.luo@linux.dev>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sun, 23 Aug 2026 11:55:54 +0800 you wrote:
> From: Xuanqiang Luo <luoxuanqiang@kylinos.cn>
>
> phy_probe() initializes the PHY driver, ports, SFP upstream, and LEDs in
> stages. Its error paths do not always release only the resources acquired
> at each stage. It can also mark the PHY ready before all setup succeeds.
>
> Port setup also leaves SFP cleanup split between phy_sfp_probe(),
> phy_setup_ports(), and phy_probe(), and default port setup ignores errors
> from attaching the port to the PHY driver.
>
> [...]
Here is the summary with links:
- [net,v5,1/6] net: phy: split phy_probe() error paths
https://git.kernel.org/netdev/net-next/c/b6d201d97145
- [net,v5,2/6] net: phy: unregister SFP upstream before port cleanup
https://git.kernel.org/netdev/net-next/c/f558204abcb9
- [net,v5,3/6] net: phy: set PHY_READY after LED setup
https://git.kernel.org/netdev/net-next/c/52dd7eb1a33e
- [net,v5,4/6] net: phy: call driver remove when core initialization fails
https://git.kernel.org/netdev/net-next/c/afd5aecd3c07
- [net,v5,5/6] net: phy: propagate errors from default port setup
https://git.kernel.org/netdev/net-next/c/48378efebbe7
- [net,v5,6/6] net: phy: avoid double-free after LED trigger registration failure
https://git.kernel.org/netdev/net-next/c/f7f619ecda57
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-08-31 0:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-23 3:55 [PATCH net v5 0/6] net: phy: fix cleanup after probe failure Xuanqiang Luo
2026-08-23 3:55 ` [PATCH net v5 1/6] net: phy: split phy_probe() error paths Xuanqiang Luo
2026-08-31 7:58 ` Maxime Chevallier
2026-08-23 3:55 ` [PATCH net v5 2/6] net: phy: unregister SFP upstream before port cleanup Xuanqiang Luo
2026-08-31 7:58 ` Maxime Chevallier
2026-08-23 3:55 ` [PATCH net v5 3/6] net: phy: set PHY_READY after LED setup Xuanqiang Luo
2026-08-23 3:55 ` [PATCH net v5 4/6] net: phy: call driver remove when core initialization fails Xuanqiang Luo
2026-08-23 3:55 ` [PATCH net v5 5/6] net: phy: propagate errors from default port setup Xuanqiang Luo
2026-08-23 3:56 ` [PATCH net v5 6/6] net: phy: avoid double-free after LED trigger registration failure Xuanqiang Luo
2026-08-27 11:40 ` Paolo Abeni
2026-08-31 0:30 ` 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=178813621634.3966634.2247622864690119590.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=chleroy@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hao.guan@siflower.com.cn \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=luoxuanqiang@kylinos.cn \
--cc=maxime.chevallier@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=qingfang.deng@siflower.com.cn \
--cc=xuanqiang.luo@linux.dev \
/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