From: Suman Ghosh <sumang@marvell.com>
To: <sgoutham@marvell.com>, <gakula@marvell.com>,
<sbhatta@marvell.com>, <hkelam@marvell.com>,
<davem@davemloft.net>, <edumazet@google.com>, <kuba@kernel.org>,
<pabeni@redhat.com>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <lcherian@marvell.com>,
<jerinj@marvell.com>, <simon.horman@corigine.com>
Cc: Suman Ghosh <sumang@marvell.com>
Subject: [net-next PATCH V2 0/2] octeontx2-af: TC flower offload changes
Date: Sun, 30 Jul 2023 20:01:05 +0530 [thread overview]
Message-ID: <20230730143107.2845172-1-sumang@marvell.com> (raw)
This patchset includes minor code restructuring related to TC
flower offload for outer vlan and adding support for TC inner
vlan offload.
Patch #1 Code restructure to handle TC flower outer vlan offload
Patch #2 Add TC flower offload support for inner vlan
Suman Ghosh (2):
octeontx2-af: Code restructure to handle TC outer VLAN offload
octeontx2-af: TC flower offload support for inner VLAN
v2 changes:
1. Fixed checkpatch errors in file
drivers/net/ethernet/marvell/octeontx2/nic/otx2_tc.c
2. Updated cover letter subject
.../net/ethernet/marvell/octeontx2/af/mbox.h | 1 +
.../net/ethernet/marvell/octeontx2/af/npc.h | 3 +
.../marvell/octeontx2/af/rvu_debugfs.c | 5 +
.../marvell/octeontx2/af/rvu_npc_fs.c | 13 +++
.../ethernet/marvell/octeontx2/nic/otx2_tc.c | 105 +++++++++++-------
5 files changed, 89 insertions(+), 38 deletions(-)
--
2.25.1
next reply other threads:[~2023-07-30 14:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-30 14:31 Suman Ghosh [this message]
2023-07-30 14:31 ` [net-next PATCH V2 1/2] octeontx2-af: Code restructure to handle TC outer VLAN offload Suman Ghosh
2023-07-31 17:20 ` Jesse Brandeburg
2023-07-30 14:31 ` [net-next PATCH V2 2/2] octeontx2-af: TC flower offload support for inner VLAN Suman Ghosh
2023-07-31 17:24 ` Jesse Brandeburg
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=20230730143107.2845172-1-sumang@marvell.com \
--to=sumang@marvell.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gakula@marvell.com \
--cc=hkelam@marvell.com \
--cc=jerinj@marvell.com \
--cc=kuba@kernel.org \
--cc=lcherian@marvell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sbhatta@marvell.com \
--cc=sgoutham@marvell.com \
--cc=simon.horman@corigine.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