From: patchwork-bot+netdevbpf@kernel.org
To: James Hilliard <james.hilliard1@gmail.com>
Cc: netdev@vger.kernel.org, pabeni@redhat.com, kuba@kernel.org,
maxime.chevallier@bootlin.com, andrew+netdev@lunn.ch,
edumazet@kernel.org, mcoquelin.stm32@gmail.com,
alexandre.torgue@foss.st.com, fancer.lancer@gmail.com,
davem@davemloft.net, nb@tipi-net.de,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v3] net: stmmac: unwind the WoL IRQ after a safety IRQ request failure
Date: Mon, 19 Oct 2026 13:40:04 +0000 [thread overview]
Message-ID: <179241720453.2644569.6506845719154683565.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261013-stmmac-irq-unwind-v3-1-fff4e2db805a@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Tue, 13 Oct 2026 11:37:11 -0600 you wrote:
> The safety IRQ is requested after the MAC and optional WoL IRQs. If its
> request fails, stmmac_free_irq() frees the unregistered safety IRQ and
> leaks the WoL handler. This can warn about an already-free IRQ and make
> the next open fail.
>
> Move the safety and WoL cleanup labels into reverse acquisition order.
>
> [...]
Here is the summary with links:
- [net-next,v3] net: stmmac: unwind the WoL IRQ after a safety IRQ request failure
https://git.kernel.org/netdev/net-next/c/ecb8b18051a1
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-19 13:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 17:37 [PATCH net-next v3] net: stmmac: unwind the WoL IRQ after a safety IRQ request failure James Hilliard
2026-10-19 13: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=179241720453.2644569.6506845719154683565.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=fancer.lancer@gmail.com \
--cc=james.hilliard1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.chevallier@bootlin.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=nb@tipi-net.de \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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