mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: YuanZhe Liu <25031212351@stu.xidian.edu.cn>
Cc: Thangaraj.S@microchip.com, UNGLinuxDriver@microchip.com,
	netdev@vger.kernel.org, linux-usb@vger.kernel.org,
	linux-kernel@vger.kernel.org, andrew+netdev@lunn.ch,
	linux@armlinux.org.uk, o.rempel@pengutronix.de,
	stable@vger.kernel.org, byu@xidian.edu.cn,
	wencheng@xidian.edu.cn
Subject: Re: [PATCH net v2] net: usb: lan78xx: let unregister_netdev() stop phylink
Date: Tue, 10 Nov 2026 18:23:04 +0000	[thread overview]
Message-ID: <179433498467.4118637.205536379890905372.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261031165213.2738-1-25031212351@stu.xidian.edu.cn>

Hello:

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

On Sun,  1 Nov 2026 00:52:13 +0800 you wrote:
> lan78xx_disconnect() stops phylink before unregistering the net device.
> phylink_start() is only called from lan78xx_open(), so when the device is
> unplugged before the interface has been brought up, the attached PHY is
> still in PHY_READY and phy_stop() reports:
> 
>   called from state READY
>   WARNING: drivers/net/phy/phy.c:1670 at phy_stop+0xad/0x380
> 
> [...]

Here is the summary with links:
  - [net,v2] net: usb: lan78xx: let unregister_netdev() stop phylink
    https://git.kernel.org/netdev/net/c/928012824561

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-11-10 18:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-31 16:52 YuanZhe Liu
2026-10-31 20:33 ` Andrew Lunn
2026-11-01  5:26   ` YuanZhe Liu
2026-11-01 19:22     ` Andrew Lunn
2026-11-01 16:52 ` netdev-bot+sashiko
2026-11-03  5:31 ` Oleksij Rempel
2026-11-10 18:23 ` 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=179433498467.4118637.205536379890905372.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=25031212351@stu.xidian.edu.cn \
    --cc=Thangaraj.S@microchip.com \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=byu@xidian.edu.cn \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=netdev@vger.kernel.org \
    --cc=o.rempel@pengutronix.de \
    --cc=stable@vger.kernel.org \
    --cc=wencheng@xidian.edu.cn \
    /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®