From: patchwork-bot+netdevbpf@kernel.org
To: <edward.cree@amd.com>
Cc: linux-net-drivers@amd.com, davem@davemloft.net, kuba@kernel.org,
pabeni@redhat.com, edumazet@google.com, ecree.xilinx@gmail.com,
netdev@vger.kernel.org, habetsm.xilinx@gmail.com
Subject: Re: [PATCH v2 net-next 0/6] sfc: TC encap actions offload
Date: Sat, 10 Jun 2023 07:21:34 +0000 [thread overview]
Message-ID: <168638169464.9909.10938668183396287229.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1686240142.git.ecree.xilinx@gmail.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 8 Jun 2023 17:42:29 +0100 you wrote:
> From: Edward Cree <ecree.xilinx@gmail.com>
>
> This series adds support for offloading TC tunnel_key set actions to the
> EF100 driver, supporting VxLAN and GENEVE tunnels over IPv4 or IPv6.
>
> Edward Cree (6):
> sfc: add fallback action-set-lists for TC offload
> sfc: some plumbing towards TC encap action offload
> sfc: add function to atomically update a rule in the MAE
> sfc: MAE functions to create/update/delete encap headers
> sfc: neighbour lookup for TC encap action offload
> sfc: generate encap headers for TC offload
>
> [...]
Here is the summary with links:
- [v2,net-next,1/6] sfc: add fallback action-set-lists for TC offload
https://git.kernel.org/netdev/net-next/c/e16ca7fb9ffb
- [v2,net-next,2/6] sfc: some plumbing towards TC encap action offload
https://git.kernel.org/netdev/net-next/c/b4da4235dc69
- [v2,net-next,3/6] sfc: add function to atomically update a rule in the MAE
https://git.kernel.org/netdev/net-next/c/69819d3bc408
- [v2,net-next,4/6] sfc: MAE functions to create/update/delete encap headers
https://git.kernel.org/netdev/net-next/c/f1363154c474
- [v2,net-next,5/6] sfc: neighbour lookup for TC encap action offload
https://git.kernel.org/netdev/net-next/c/7e5e7d800011
- [v2,net-next,6/6] sfc: generate encap headers for TC offload
https://git.kernel.org/netdev/net-next/c/a1e82162af0b
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-06-10 7:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-08 16:42 [PATCH v2 net-next 0/6] sfc: TC encap actions offload edward.cree
2023-06-08 16:42 ` [PATCH v2 net-next 1/6] sfc: add fallback action-set-lists for TC offload edward.cree
2023-06-09 9:37 ` Simon Horman
2023-06-08 16:42 ` [PATCH v2 net-next 2/6] sfc: some plumbing towards TC encap action offload edward.cree
2023-06-09 9:35 ` Simon Horman
2023-06-08 16:42 ` [PATCH v2 net-next 3/6] sfc: add function to atomically update a rule in the MAE edward.cree
2023-06-09 9:35 ` Simon Horman
2023-06-08 16:42 ` [PATCH v2 net-next 4/6] sfc: MAE functions to create/update/delete encap headers edward.cree
2023-06-09 9:36 ` Simon Horman
2023-06-08 16:42 ` [PATCH v2 net-next 5/6] sfc: neighbour lookup for TC encap action offload edward.cree
2023-06-09 9:37 ` Simon Horman
2023-06-09 10:25 ` Pieter Jansen van Vuuren
2023-06-08 16:42 ` [PATCH v2 net-next 6/6] sfc: generate encap headers for TC offload edward.cree
2023-06-09 9:36 ` Simon Horman
2023-06-09 10:29 ` Pieter Jansen van Vuuren
2023-06-10 7:21 ` 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=168638169464.9909.10938668183396287229.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=ecree.xilinx@gmail.com \
--cc=edumazet@google.com \
--cc=edward.cree@amd.com \
--cc=habetsm.xilinx@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-net-drivers@amd.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).