From: patchwork-bot+netdevbpf@kernel.org
To: Bo Sun <bo@mboxify.com>
Cc: sgoutham@marvell.com, gakula@marvell.com, kuba@kernel.org,
pabeni@redhat.com, sbhatta@marvell.com, hkelam@marvell.com,
horms@kernel.org, bbhushan2@marvell.com, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, sumang@marvell.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v2 0/2] octeontx2: fix bitmap leaks in PF and VF
Date: Wed, 01 Oct 2025 00:40:08 +0000 [thread overview]
Message-ID: <175927920875.2252526.3237930601747608854.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250930061236.31359-1-bo@mboxify.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 30 Sep 2025 14:12:34 +0800 you wrote:
> Two small patches that free the AF_XDP bitmap in the PF and VF
> remove paths. Both carry the same Fixes tag and should go to
> stable.
>
> Changes in v2:
> - Add correct [PATCH net v2] subject prefix
> - CC the sign-off authors that introduced the leak and everyone
> returned by scripts/get_maintainer.pl
>
> [...]
Here is the summary with links:
- [net,v2,1/2] octeontx2-vf: fix bitmap leak
https://git.kernel.org/netdev/net/c/cd9ea7da41a4
- [net,v2,2/2] octeontx2-pf: fix bitmap leak
https://git.kernel.org/netdev/net/c/92e9f4faffca
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:[~2025-10-01 0:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-30 6:12 Bo Sun
2025-09-30 6:12 ` [PATCH net v2 1/2] octeontx2-vf: fix bitmap leak Bo Sun
2025-09-30 6:12 ` [PATCH net v2 2/2] octeontx2-pf: " Bo Sun
2025-10-01 0: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=175927920875.2252526.3237930601747608854.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=bbhushan2@marvell.com \
--cc=bo@mboxify.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gakula@marvell.com \
--cc=hkelam@marvell.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sbhatta@marvell.com \
--cc=sgoutham@marvell.com \
--cc=sumang@marvell.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®