From: Subrat Pandey <subratp@marvell.com>
To: <linux-kernel@vger.kernel.org>, <netdev@vger.kernel.org>
Cc: <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>,
<subratp@marvell.com>
Subject: [PATCH net v3 0/2] octeontx2: Misc fixes for RVU drivers
Date: Wed, 12 Aug 2026 17:22:56 +0530 [thread overview]
Message-ID: <20260812115258.773319-1-subratp@marvell.com> (raw)
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.
Changes in v3:
- patch 1: Unify the BPID index logic into a shared otx2_get_bpid_idx()
helper, dropping the per-file #ifdef CONFIG_DCB.
- patch 2: Extend the sc.max fix to the SC stats loop in
mcs_clear_all_stats(); add Fixes: tag.
Changes in v2:
- Dropped "octeontx2-af: Fix mcs string buffer size", will
re-target it to net-next.
Baha Mesleh (1):
octeontx2-af: mcs: Fix SC resource cleanup loop
Geetha sowjanya (1):
octeontx2-pf: Fix aura BPID assignment when CONFIG_DCB is enabled
drivers/net/ethernet/marvell/octeontx2/af/mcs.c | 4 ++--
.../net/ethernet/marvell/octeontx2/nic/cn20k.c | 11 +----------
.../ethernet/marvell/octeontx2/nic/otx2_common.c | 16 ++++++----------
.../ethernet/marvell/octeontx2/nic/otx2_common.h | 8 ++++++++
4 files changed, 17 insertions(+), 22 deletions(-)
--
2.43.0
next reply other threads:[~2026-08-12 11:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-12 11:52 Subrat Pandey [this message]
2026-08-12 11:52 ` [PATCH net v3 1/2] octeontx2-pf: Fix aura BPID assignment when CONFIG_DCB is enabled Subrat Pandey
2026-08-17 23:34 ` Jakub Kicinski
2026-08-12 11:52 ` [PATCH net v3 2/2] octeontx2-af: mcs: Fix SC resource cleanup loop Subrat Pandey
2026-08-17 23:34 ` Jakub Kicinski
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=20260812115258.773319-1-subratp@marvell.com \
--to=subratp@marvell.com \
--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 \
/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.