From: patchwork-bot+netdevbpf@kernel.org
To: Subrat Pandey <subratp@marvell.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
pabeni@redhat.com, kuba@kernel.org, edumazet@google.com,
davem@davemloft.net, andrew+netdev@lunn.ch, sbhatta@marvell.com,
rkannoth@marvell.com, gakula@marvell.com, sgoutham@marvell.com
Subject: Re: [PATCH net v7 0/2] octeontx2: Misc fixes for RVU drivers
Date: Tue, 29 Sep 2026 01:40:06 +0000 [thread overview]
Message-ID: <179064600678.210624.13233942205571941938.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260922102149.2078168-1-subratp@marvell.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 22 Sep 2026 15:51:47 +0530 you wrote:
> A few independent fixes for the Marvell OcteonTX2 (RVU AF/PF) drivers:
>
> - Fix aura/CQ BPID assignment under CONFIG_DCB, which assumed
> queue_to_pfc_map was always allocated (not true for SDP VFs).
> - Fix the SC resource cleanup loop that iterated over secy.max
> instead of sc.max.
>
> [...]
Here is the summary with links:
- [net,v7,1/2] octeontx2-pf: Fix aura BPID assignment when CONFIG_DCB is enabled
https://git.kernel.org/netdev/net/c/056994563935
- [net,v7,2/2] octeontx2-af: mcs: Fix SC resource cleanup loop
https://git.kernel.org/netdev/net/c/cdef07f3002f
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-29 1:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 10:21 [PATCH net v7 0/2] octeontx2: Misc fixes for RVU drivers Subrat Pandey
2026-09-22 10:21 ` [PATCH net v7 1/2] octeontx2-pf: Fix aura BPID assignment when CONFIG_DCB is enabled Subrat Pandey
2026-09-22 10:21 ` [PATCH net v7 2/2] octeontx2-af: mcs: Fix SC resource cleanup loop Subrat Pandey
2026-09-27 10:44 ` [PATCH net v7 0/2] octeontx2: Misc fixes for RVU drivers Simon Horman
2026-09-29 1: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=179064600678.210624.13233942205571941938.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gakula@marvell.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rkannoth@marvell.com \
--cc=sbhatta@marvell.com \
--cc=sgoutham@marvell.com \
--cc=subratp@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 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.