From: patchwork-bot+netdevbpf@kernel.org
To: Fedor Pchelkin <pchelkin@ispras.ru>
Cc: nicolas.ferre@microchip.com, claudiu.beznea@tuxon.dev,
theo.lebrun@bootlin.com, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, ztong0001@gmail.com, bfolta@cadence.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
lvc-project@linuxtesting.org
Subject: Re: [PATCH net 1/2] net: macb: fix clk handling on PCI glue driver removal
Date: Thu, 02 Apr 2026 03:00:11 +0000 [thread overview]
Message-ID: <177509881178.3966658.17912738150226737431.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260330184542.626619-1-pchelkin@ispras.ru>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 30 Mar 2026 21:45:40 +0300 you wrote:
> platform_device_unregister() may still want to use the registered clks
> during runtime resume callback.
>
> Note that there is a commit d82d5303c4c5 ("net: macb: fix use after free
> on rmmod") that addressed the similar problem of clk vs platform device
> unregistration but just moved the bug to another place.
>
> [...]
Here is the summary with links:
- [net,1/2] net: macb: fix clk handling on PCI glue driver removal
https://git.kernel.org/netdev/net/c/ce8fe5287b87
- [net,2/2] net: macb: properly unregister fixed rate clocks
https://git.kernel.org/netdev/net/c/f0f367a4f459
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-04-02 3:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-30 18:45 [PATCH net 1/2] net: macb: fix clk handling on PCI glue driver removal Fedor Pchelkin
2026-03-30 18:45 ` [PATCH net 2/2] net: macb: properly unregister fixed rate clocks Fedor Pchelkin
2026-04-02 3:00 ` 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=177509881178.3966658.17912738150226737431.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=bfolta@cadence.com \
--cc=claudiu.beznea@tuxon.dev \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lvc-project@linuxtesting.org \
--cc=netdev@vger.kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=pabeni@redhat.com \
--cc=pchelkin@ispras.ru \
--cc=theo.lebrun@bootlin.com \
--cc=ztong0001@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox