From: patchwork-bot+netdevbpf@kernel.org
To: <edward.cree@amd.com>
Cc: linux-net-drivers@amd.com, davem@davemloft.net, kuba@kernel.org,
edumazet@google.com, pabeni@redhat.com, ecree.xilinx@gmail.com,
netdev@vger.kernel.org, habetsm.xilinx@gmail.com
Subject: Re: [PATCH net-next 0/2] sfc: support conntrack NAT offload
Date: Sun, 15 Oct 2023 13:30:24 +0000 [thread overview]
Message-ID: <169737662410.24568.17382832877055092106.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1696974554.git.ecree.xilinx@gmail.com>
Hello:
This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Tue, 10 Oct 2023 22:51:58 +0100 you wrote:
> From: Edward Cree <ecree.xilinx@gmail.com>
>
> The EF100 MAE supports performing NAT (and NPT) on packets which match in
> the conntrack table. This series adds that capability to the driver.
>
> Edward Cree (2):
> sfc: parse mangle actions (NAT) in conntrack entries
> sfc: support offloading ct(nat) action in RHS rules
>
> [...]
Here is the summary with links:
- [net-next,1/2] sfc: parse mangle actions (NAT) in conntrack entries
https://git.kernel.org/netdev/net-next/c/38f9a08a3e6a
- [net-next,2/2] sfc: support offloading ct(nat) action in RHS rules
https://git.kernel.org/netdev/net-next/c/0c7fe3b3720e
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-10-15 13:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-10 21:51 [PATCH net-next 0/2] sfc: support conntrack NAT offload edward.cree
2023-10-10 21:51 ` [PATCH net-next 1/2] sfc: parse mangle actions (NAT) in conntrack entries edward.cree
2023-10-10 21:52 ` [PATCH net-next 2/2] sfc: support offloading ct(nat) action in RHS rules edward.cree
2023-10-13 11:26 ` [PATCH net-next 0/2] sfc: support conntrack NAT offload Simon Horman
2023-10-15 13: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=169737662410.24568.17382832877055092106.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).