From: patchwork-bot+netdevbpf@kernel.org
To: Nitin Shetty J <nshettyj@marvell.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
psatheesh@marvell.com, sgoutham@marvell.com,
rkannoth@marvell.com, gakula@marvell.com, sbhatta@marvell.com,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com
Subject: Re: [PATCH net-next] octeontx2-af: add support for custom L2 header
Date: Fri, 24 Jul 2026 23:20:26 +0000 [thread overview]
Message-ID: <178493522613.3348566.6579358640988949.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260715072035.617544-1-nshettyj@marvell.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 15 Jul 2026 12:50:34 +0530 you wrote:
> From: Satheesh Paul A <psatheesh@marvell.com>
>
> Add packet parsing support for custom L2 headers. Also add support
> to include a field from the custom header for flow tag generation.
>
> Introduce a new flow key type NIX_FLOW_KEY_TYPE_CH_LEN_90B which
> maps to the NPC_LT_LA_CUSTOM_L2_90B_ETHER layer type. This extracts
> a 2-byte field at a 24-byte offset in layer A to be used in flow
> tag generation.
>
> [...]
Here is the summary with links:
- [net-next] octeontx2-af: add support for custom L2 header
https://git.kernel.org/netdev/net-next/c/e2834100751a
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-07-24 23:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-15 7:20 [PATCH net-next] octeontx2-af: add support for custom L2 header nshettyj
2026-07-24 23:20 ` 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=178493522613.3348566.6579358640988949.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=nshettyj@marvell.com \
--cc=pabeni@redhat.com \
--cc=psatheesh@marvell.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.