netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: <edward.cree@amd.com>
Cc: netdev@vger.kernel.org, linux-net-drivers@amd.com,
	davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
	edumazet@google.com, habetsm.xilinx@gmail.com,
	ecree.xilinx@gmail.com
Subject: Re: [PATCH v2 net-next 0/5] sfc: add basic flower matches to offload
Date: Sat, 05 Nov 2022 03:10:17 +0000	[thread overview]
Message-ID: <166761781705.20771.9065271264242447801.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1667412458.git.ecree.xilinx@gmail.com>

Hello:

This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:

On Thu, 3 Nov 2022 15:27:26 +0000 you wrote:
> From: Edward Cree <ecree.xilinx@gmail.com>
> 
> Support offloading TC flower rules with matches on L2-L4 fields.
> 
> Changed in v2:
>  * changed CHECK macro to not hide control flow.  Annoyingly, gcc complains
>    if we don't use the result of the OR-expression we're using to get short-
>    circuiting behaviour (ensuring we only report the first error), so we
>    have to have an if-statement that's semantically redundant.
>  * added explanation to patch #1 of why these checks aren't vital for
>    correctness (and thus don't need to have a Fixes tag or go to net).
> 
> [...]

Here is the summary with links:
  - [v2,net-next,1/5] sfc: check recirc_id match caps before MAE offload
    https://git.kernel.org/netdev/net-next/c/f0b59ad11e29
  - [v2,net-next,2/5] sfc: add Layer 2 matches to ef100 TC offload
    https://git.kernel.org/netdev/net-next/c/6d1c604d1098
  - [v2,net-next,3/5] sfc: add Layer 3 matches to ef100 TC offload
    https://git.kernel.org/netdev/net-next/c/c178dff3f92d
  - [v2,net-next,4/5] sfc: add Layer 3 flag matches to ef100 TC offload
    https://git.kernel.org/netdev/net-next/c/5ca7ef293866
  - [v2,net-next,5/5] sfc: add Layer 4 matches to ef100 TC offload
    https://git.kernel.org/netdev/net-next/c/5d1d24da00db

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



      parent reply	other threads:[~2022-11-05  3:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-03 15:27 [PATCH v2 net-next 0/5] sfc: add basic flower matches to offload edward.cree
2022-11-03 15:27 ` [PATCH v2 net-next 1/5] sfc: check recirc_id match caps before MAE offload edward.cree
2022-11-03 15:27 ` [PATCH v2 net-next 2/5] sfc: add Layer 2 matches to ef100 TC offload edward.cree
2022-11-03 15:27 ` [PATCH v2 net-next 3/5] sfc: add Layer 3 " edward.cree
2022-11-03 15:27 ` [PATCH v2 net-next 4/5] sfc: add Layer 3 flag " edward.cree
2022-11-03 15:27 ` [PATCH v2 net-next 5/5] sfc: add Layer 4 " edward.cree
2022-11-05  3:10 ` 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=166761781705.20771.9065271264242447801.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).