From: patchwork-bot+netdevbpf@kernel.org
To: =?utf-8?q?Th=C3=A9o_Lebrun_=3Ctheo=2Elebrun=40bootlin=2Ecom=3E?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org
Cc: conor.dooley@microchip.com, andrew+netdev@lunn.ch,
davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, sean.anderson@linux.dev, atenart@kernel.org,
edumazet@kernel.org, nicolas.ferre@microchip.com,
linux@armlinux.org.uk, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, nb@tipi-net.de,
vladimir.kondratiev@mobileye.com, gregory.clement@bootlin.com,
tawfik.bayouk@mobileye.com, thomas.petazzoni@bootlin.com,
maxime.chevallier@bootlin.com, stable@vger.kernel.org
Subject: Re: [PATCH net v2 0/3] net: macb: fix close races (and RX refill error handling)
Date: Wed, 30 Sep 2026 01:50:09 +0000 [thread overview]
Message-ID: <179073300902.1202110.8723363040296722029.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260925-macb-close-v2-0-360efa565914@bootlin.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 25 Sep 2026 15:59:33 +0200 you wrote:
> The context-swapping series [0] has been ongoing for a while. The most
> interesting part is a proper hardware shutdown sequence, which is truly
> lacking in other parts of the MACB driver: at close, at suspend and in
> the HRESP error task.
>
> Instead of introducing that sequence for a new feature, apply it now to
> fix the main offender, the close path. That fixes the races listed in
> patch 3 and will allow the sequence to be reused later.
>
> [...]
Here is the summary with links:
- [net,v2,1/3] net: macb: never give hardware a NULL RX buffer
https://git.kernel.org/netdev/net-next/c/efd90b64ce25
- [net,v2,2/3] net: macb: propagate RX ring refill errors
https://git.kernel.org/netdev/net-next/c/9ea465c4fbaf
- [net,v2,3/3] net: macb: quiesce IRQs and drain BH on interface close
https://git.kernel.org/netdev/net-next/c/4fcaed2cb1d8
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-09-30 1:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-25 13:59 Théo Lebrun
2026-09-25 13:59 ` [PATCH net v2 1/3] net: macb: never give hardware a NULL RX buffer Théo Lebrun
2026-09-29 2:00 ` netdev-bot+sashiko
2026-09-30 1:45 ` Jakub Kicinski
2026-09-25 13:59 ` [PATCH net v2 2/3] net: macb: propagate RX ring refill errors Théo Lebrun
2026-09-25 14:20 ` Nicolai Buchwitz
2026-09-29 2:00 ` netdev-bot+sashiko
2026-09-25 13:59 ` [PATCH net v2 3/3] net: macb: quiesce IRQs and drain BH on interface close Théo Lebrun
2026-09-29 2:01 ` netdev-bot+sashiko
2026-09-30 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=179073300902.1202110.8723363040296722029.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc==?utf-8?q?Th=C3=A9o_Lebrun_=3Ctheo=2Elebrun=40bootlin=2Ecom=3E?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
--cc=andrew+netdev@lunn.ch \
--cc=atenart@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=gregory.clement@bootlin.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=maxime.chevallier@bootlin.com \
--cc=nb@tipi-net.de \
--cc=netdev@vger.kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=pabeni@redhat.com \
--cc=sean.anderson@linux.dev \
--cc=stable@vger.kernel.org \
--cc=tawfik.bayouk@mobileye.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=vladimir.kondratiev@mobileye.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
all inboxes | Powered by JetHome®