From: patchwork-bot+netdevbpf@kernel.org
To: Pieter Jansen van Vuuren <pieter.jansen-van-vuuren@amd.com>
Cc: netdev@vger.kernel.org, linux-net-drivers@amd.com,
davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
edumazet@google.com, ecree.xilinx@gmail.com,
habetsm.xilinx@gmail.com
Subject: Re: [PATCH net-next v2 0/6] sfc: introduce eth, ipv4 and ipv6 pedit offloads
Date: Sun, 27 Aug 2023 06:02:26 +0000 [thread overview]
Message-ID: <169311614695.23659.11317146439281618197.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230824112842.47883-1-pieter.jansen-van-vuuren@amd.com>
Hello:
This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Thu, 24 Aug 2023 12:28:36 +0100 you wrote:
> This set introduces mac source and destination pedit set action offloads.
> It also adds offload for ipv4 ttl and ipv6 hop limit pedit set action as
> well pedit add actions that would result in the same semantics as
> decrementing the ttl and hop limit.
>
> v2:
> - fix 'efx_tc_mangle' kdoc which was orphaned when adding 'efx_tc_pedit_add'.
> - add description of 'match' in 'efx_tc_mangle' kdoc.
> - correct some inconsistent kdoc indentation.
>
> [...]
Here is the summary with links:
- [net-next,v2,1/6] sfc: introduce ethernet pedit set action infrastructure
https://git.kernel.org/netdev/net-next/c/439c4be98318
- [net-next,v2,2/6] sfc: add mac source and destination pedit action offload
https://git.kernel.org/netdev/net-next/c/0c676503bd4f
- [net-next,v2,3/6] sfc: add decrement ttl by offloading set ipv4 ttl actions
https://git.kernel.org/netdev/net-next/c/66f728872636
- [net-next,v2,4/6] sfc: add decrement ipv6 hop limit by offloading set hop limit actions
https://git.kernel.org/netdev/net-next/c/9dbc8d2b9a02
- [net-next,v2,5/6] sfc: introduce pedit add actions on the ipv4 ttl field
https://git.kernel.org/netdev/net-next/c/64848f062e33
- [net-next,v2,6/6] sfc: extend pedit add action to handle decrement ipv6 hop limit
https://git.kernel.org/netdev/net-next/c/e8e0bd60e483
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-27 6:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-24 11:28 [PATCH net-next v2 0/6] sfc: introduce eth, ipv4 and ipv6 pedit offloads Pieter Jansen van Vuuren
2023-08-24 11:28 ` [PATCH net-next v2 1/6] sfc: introduce ethernet pedit set action infrastructure Pieter Jansen van Vuuren
2023-08-24 11:28 ` [PATCH net-next v2 2/6] sfc: add mac source and destination pedit action offload Pieter Jansen van Vuuren
2023-08-24 11:28 ` [PATCH net-next v2 3/6] sfc: add decrement ttl by offloading set ipv4 ttl actions Pieter Jansen van Vuuren
2023-08-24 11:28 ` [PATCH net-next v2 4/6] sfc: add decrement ipv6 hop limit by offloading set hop limit actions Pieter Jansen van Vuuren
2023-08-24 11:28 ` [PATCH net-next v2 5/6] sfc: introduce pedit add actions on the ipv4 ttl field Pieter Jansen van Vuuren
2023-08-24 11:28 ` [PATCH net-next v2 6/6] sfc: extend pedit add action to handle decrement ipv6 hop limit Pieter Jansen van Vuuren
2023-08-25 10:27 ` [PATCH net-next v2 0/6] sfc: introduce eth, ipv4 and ipv6 pedit offloads Simon Horman
2023-08-27 6:02 ` 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=169311614695.23659.11317146439281618197.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=habetsm.xilinx@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-net-drivers@amd.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pieter.jansen-van-vuuren@amd.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).