From: patchwork-bot+netdevbpf@kernel.org
To: Andrew Lunn <andrew@lunn.ch>
Cc: netdev@vger.kernel.org, hkallweit1@gmail.com,
ansuelsmth@gmail.com, rmk+kernel@armlinux.org.uk,
stable@vger.kernel.org, f.fainelli@gmail.com
Subject: Re: [PATCH net] net: phy: Manual remove LEDs to ensure correct ordering
Date: Sun, 18 Jun 2023 16:40:18 +0000 [thread overview]
Message-ID: <168710641899.5271.11988489535830400301.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230617155500.4005881-1-andrew@lunn.ch>
Hello:
This patch was applied to netdev/net.git (main)
by David S. Miller <davem@davemloft.net>:
On Sat, 17 Jun 2023 17:55:00 +0200 you wrote:
> If the core is left to remove the LEDs via devm_, it is performed too
> late, after the PHY driver is removed from the PHY. This results in
> dereferencing a NULL pointer when the LED core tries to turn the LED
> off before destroying the LED.
>
> Manually unregister the LEDs at a safe point in phy_remove.
>
> [...]
Here is the summary with links:
- [net] net: phy: Manual remove LEDs to ensure correct ordering
https://git.kernel.org/netdev/net/c/c938ab4da0eb
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2023-06-18 16:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-17 15:55 [PATCH net] net: phy: Manual remove LEDs to ensure correct ordering Andrew Lunn
2023-06-18 16:40 ` patchwork-bot+netdevbpf [this message]
2023-06-21 14:04 ` Florian Fainelli
2023-06-21 15:01 ` Andrew Lunn
2023-06-21 17:04 ` Russell King (Oracle)
2023-06-21 17:12 ` Florian Fainelli
2023-06-21 17:52 ` Russell King (Oracle)
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=168710641899.5271.11988489535830400301.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=ansuelsmth@gmail.com \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=rmk+kernel@armlinux.org.uk \
--cc=stable@vger.kernel.org \
/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.