All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Aleksei Sviridkin <f@lex.la>
Cc: andrew@lunn.ch, hkallweit1@gmail.com, linux@armlinux.org.uk,
	netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, linux-kernel@vger.kernel.org,
	f.fainelli@gmail.com, woojung.huh@microchip.com,
	vladimir.oltean@nxp.com, maxime.chevallier@bootlin.com
Subject: Re: [PATCH net-next v6 0/2] net: phy: fix a second attach of an attached PHY and the module put on detach
Date: Sat, 17 Oct 2026 01:50:13 +0000	[thread overview]
Message-ID: <179220181326.1055958.8232686997643079264.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261013151200.2473464-1-f@lex.la>

Hello:

This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Tue, 13 Oct 2026 18:11:58 +0300 you wrote:
> Two phylib fixes found on a Keenetic KN-1012 (MT7981) while chasing a
> PHY driver unbind race. A second attach of an attached PHY tears down
> the first consumer, and a detach after a driver unbind leaks the module
> reference.
> 
> 1: refuse a second attach before the driver module is taken or the
>    generic driver bound.
> 2: put the module the attach pinned, not whatever driver is bound at
>    detach.
> 
> [...]

Here is the summary with links:
  - [net-next,v6,1/2] net: phy: refuse a second attach before touching the PHY
    https://git.kernel.org/netdev/net-next/c/fa38468cd26b
  - [net-next,v6,2/2] net: phy: put the driver module the attach took
    https://git.kernel.org/netdev/net-next/c/7151b86654fa

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-10-17  1:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-13 15:11 [PATCH net-next v6 0/2] net: phy: fix a second attach of an attached PHY and the module put on detach Aleksei Sviridkin
2026-10-13 15:11 ` [PATCH net-next v6 1/2] net: phy: refuse a second attach before touching the PHY Aleksei Sviridkin
2026-10-14 11:51   ` Andrew Lunn
2026-10-13 15:12 ` [PATCH net-next v6 2/2] net: phy: put the driver module the attach took Aleksei Sviridkin
2026-10-17  1:50 ` 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=179220181326.1055958.8232686997643079264.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=f.fainelli@gmail.com \
    --cc=f@lex.la \
    --cc=hkallweit1@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=maxime.chevallier@bootlin.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=vladimir.oltean@nxp.com \
    --cc=woojung.huh@microchip.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.