netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 v2 net-next 0/7] sfc: basic conntrack offload
Date: Wed, 09 Aug 2023 10:20:21 +0000	[thread overview]
Message-ID: <169157642102.31305.7403062205482739405.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1691415479.git.ecree.xilinx@gmail.com>

Hello:

This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:

On Mon, 7 Aug 2023 14:48:04 +0100 you wrote:
> From: Edward Cree <ecree.xilinx@gmail.com>
> 
> Support offloading tracked connections and matching against them in
>  TC chains on the PF and on representors.
> Later patch serieses will add NAT and conntrack-on-tunnel-netdevs;
>  keep it simple for now.
> 
> [...]

Here is the summary with links:
  - [v2,net-next,1/7] sfc: add MAE table machinery for conntrack table
    https://git.kernel.org/netdev/net-next/c/3bf969e88ada
  - [v2,net-next,2/7] sfc: functions to register for conntrack zone offload
    https://git.kernel.org/netdev/net-next/c/c3bb5c6acd4e
  - [v2,net-next,3/7] sfc: functions to insert/remove conntrack entries to MAE hardware
    https://git.kernel.org/netdev/net-next/c/94aa05bdc777
  - [v2,net-next,4/7] sfc: offload conntrack flow entries (match only) from CT zones
    https://git.kernel.org/netdev/net-next/c/1909387fcfcf
  - [v2,net-next,5/7] sfc: handle non-zero chain_index on TC rules
    https://git.kernel.org/netdev/net-next/c/294160251853
  - [v2,net-next,6/7] sfc: conntrack state matches in TC rules
    https://git.kernel.org/netdev/net-next/c/1dfc29be4d74
  - [v2,net-next,7/7] sfc: offload left-hand side rules for conntrack
    https://git.kernel.org/netdev/net-next/c/01ad088fb05c

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2023-08-09 10:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-07 13:48 [PATCH v2 net-next 0/7] sfc: basic conntrack offload edward.cree
2023-08-07 13:48 ` [PATCH v2 net-next 1/7] sfc: add MAE table machinery for conntrack table edward.cree
2023-08-07 13:48 ` [PATCH v2 net-next 2/7] sfc: functions to register for conntrack zone offload edward.cree
2023-08-07 13:48 ` [PATCH v2 net-next 3/7] sfc: functions to insert/remove conntrack entries to MAE hardware edward.cree
2023-08-07 13:48 ` [PATCH v2 net-next 4/7] sfc: offload conntrack flow entries (match only) from CT zones edward.cree
2023-08-07 13:48 ` [PATCH v2 net-next 5/7] sfc: handle non-zero chain_index on TC rules edward.cree
2023-08-07 13:48 ` [PATCH v2 net-next 6/7] sfc: conntrack state matches in " edward.cree
2023-08-07 13:48 ` [PATCH v2 net-next 7/7] sfc: offload left-hand side rules for conntrack edward.cree
2023-08-09 10: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=169157642102.31305.7403062205482739405.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).