From: patchwork-bot+netdevbpf@kernel.org
To: <kirankumark@marvell.com>
Cc: sgoutham@marvell.com, lcherian@marvell.com, gakula@marvell.com,
jerinj@marvell.com, hkelam@marvell.com, sbhatta@marvell.com,
davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [net-next 0/2] adding KPU profile changes for GTPU and custom
Date: Sun, 26 Sep 2021 10:30:06 +0000 [thread overview]
Message-ID: <163265220680.26415.8925595801133738113.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210924061851.680922-1-kirankumark@marvell.com>
Hello:
This series was applied to netdev/net-next.git (refs/heads/master):
On Fri, 24 Sep 2021 11:48:49 +0530 you wrote:
> From: Kiran Kumar K <kirankumark@marvell.com>
>
> Adding changes to limit the KPU processing for GTPU headers to parse
> packet up to L4 and added changes to variable length headers to parse LA
> as part of PKIND action.
>
> Kiran Kumar K (2):
> octeontx2-af: Limit KPU parsing for GTPU packets
> octeontx2-af: Optimize KPU1 processing for variable-length headers
>
> [...]
Here is the summary with links:
- [net-next,1/2] octeontx2-af: Limit KPU parsing for GTPU packets
https://git.kernel.org/netdev/net-next/c/2fae469ae238
- [net-next,2/2] octeontx2-af: Optimize KPU1 processing for variable-length headers
https://git.kernel.org/netdev/net-next/c/edadeb38dc2f
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:[~2021-09-26 10:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-24 6:18 [net-next 0/2] adding KPU profile changes for GTPU and custom kirankumark
2021-09-24 6:18 ` [net-next 1/2] octeontx2-af: Limit KPU parsing for GTPU packets kirankumark
2021-09-24 6:18 ` [net-next 2/2] octeontx2-af: Optimize KPU1 processing for variable-length headers kirankumark
2021-09-26 10: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=163265220680.26415.8925595801133738113.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=gakula@marvell.com \
--cc=hkelam@marvell.com \
--cc=jerinj@marvell.com \
--cc=kirankumark@marvell.com \
--cc=kuba@kernel.org \
--cc=lcherian@marvell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox