From: patchwork-bot+netdevbpf@kernel.org
To: Suman Ghosh <sumang@marvell.com>
Cc: 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,
jesse.brandeburg@intel.com
Subject: Re: [net-next PATCH V5 0/2] octeontx2-af: TC flower offload changes
Date: Tue, 08 Aug 2023 02:30:22 +0000 [thread overview]
Message-ID: <169146182268.15123.9072085629750422211.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230804045935.3010554-1-sumang@marvell.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 4 Aug 2023 10:29:33 +0530 you wrote:
> 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
>
> [...]
Here is the summary with links:
- [net-next,V5,1/2] octeontx2-af: Code restructure to handle TC outer VLAN offload
https://git.kernel.org/netdev/net-next/c/aa07a0f421b5
- [net-next,V5,2/2] octeontx2-af: TC flower offload support for inner VLAN
https://git.kernel.org/netdev/net-next/c/21e748354ec2
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:[~2023-08-08 2:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-04 4:59 Suman Ghosh
2023-08-04 4:59 ` [net-next PATCH V5 1/2] octeontx2-af: Code restructure to handle TC outer VLAN offload Suman Ghosh
2023-08-04 4:59 ` [net-next PATCH V5 2/2] octeontx2-af: TC flower offload support for inner VLAN Suman Ghosh
2023-08-05 7:25 ` [net-next PATCH V5 0/2] octeontx2-af: TC flower offload changes Simon Horman
2023-08-08 2:30 ` 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=169146182268.15123.9072085629750422211.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gakula@marvell.com \
--cc=hkelam@marvell.com \
--cc=jerinj@marvell.com \
--cc=jesse.brandeburg@intel.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 \
--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®