From: patchwork-bot+netdevbpf@kernel.org
To: Aleksei Sviridkin <f@lex.la>
Cc: netdev@vger.kernel.org, andrew@lunn.ch, andrew+netdev@lunn.ch,
hkallweit1@gmail.com, linux@armlinux.org.uk, davem@davemloft.net,
edumazet@kernel.org, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, olteanv@gmail.com, Thangaraj.S@microchip.com,
UNGLinuxDriver@microchip.com, steve.glendinning@shawell.net,
f.fainelli@gmail.com, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v13 0/4] net: phy: keep a PHY interrupt across a generic bind cycle
Date: Wed, 07 Oct 2026 00:40:10 +0000 [thread overview]
Message-ID: <179133361003.2844451.4683989741719599976.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261001130236.106059-1-f@lex.la>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 1 Oct 2026 16:02:32 +0300 you wrote:
> On a Keenetic KN-1012 the EN8811H PHY behind lan4 has its driver as a
> module on the root filesystem, so it binds to the generic driver first.
> phy_probe() replaces its interrupt with PHY_POLL, and nothing puts it
> back when the real driver takes over, so the PHY is polled for the rest
> of the uptime.
>
> Patches 1 and 2 put the lan78xx and smsc95xx PHY interrupts into the
> MDIO bus table entry of the PHY each driver uses, so there is a number
> to restore for them too. Patch 3 restores the interrupt from that table
> in phy_detach(). Patch 4 restores it when the generic bind fails inside
> phy_attach_direct().
>
> [...]
Here is the summary with links:
- [net,v13,1/4] net: usb: lan78xx: register the PHY interrupt with the MDIO bus
https://git.kernel.org/netdev/net-next/c/06192231d089
- [net,v13,2/4] net: usb: smsc95xx: register the PHY interrupt with the MDIO bus
https://git.kernel.org/netdev/net-next/c/2c583f49e8f0
- [net,v13,3/4] net: phy: take the interrupt back from the bus on detach
https://git.kernel.org/netdev/net-next/c/026bb4593faf
- [net,v13,4/4] net: phy: restore the interrupt when the generic bind cycle fails
https://git.kernel.org/netdev/net-next/c/4719b69bb66b
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-10-07 0:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-01 13:02 Aleksei Sviridkin
2026-10-01 13:02 ` [PATCH net v13 1/4] net: usb: lan78xx: register the PHY interrupt with the MDIO bus Aleksei Sviridkin
2026-10-05 16:52 ` Andrew Lunn
2026-10-01 13:02 ` [PATCH net v13 2/4] net: usb: smsc95xx: " Aleksei Sviridkin
2026-10-05 16:53 ` Andrew Lunn
2026-10-01 13:02 ` [PATCH net v13 3/4] net: phy: take the interrupt back from the bus on detach Aleksei Sviridkin
2026-10-05 13:26 ` netdev-bot+sashiko
2026-10-05 16:55 ` Andrew Lunn
2026-10-01 13:02 ` [PATCH net v13 4/4] net: phy: restore the interrupt when the generic bind cycle fails Aleksei Sviridkin
2026-10-07 0:40 ` 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=179133361003.2844451.4683989741719599976.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Thangaraj.S@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=f@lex.la \
--cc=hkallweit1@gmail.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=steve.glendinning@shawell.net \
/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
all inboxes | Powered by JetHome®