From: patchwork-bot+netdevbpf@kernel.org
To: <ecree@xilinx.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/6] sfc: bare bones TC offload
Date: Wed, 28 Sep 2022 08:50:17 +0000 [thread overview]
Message-ID: <166435501724.19549.11910754562202475038.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1664218348.git.ecree.xilinx@gmail.com>
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Mon, 26 Sep 2022 19:57:30 +0100 you wrote:
> From: Edward Cree <ecree.xilinx@gmail.com>
>
> This series begins the work of supporting TC flower offload on EF100 NICs.
> This is the absolute minimum viable TC implementation to get traffic to
> VFs and allow them to be tested; it supports no match fields besides
> ingress port, no actions besides mirred and drop, and no stats.
> More matches, actions, and counters will be added in subsequent patches.
>
> [...]
Here is the summary with links:
- [v2,net-next,1/6] sfc: bind blocks for TC offload on EF100
https://git.kernel.org/netdev/net-next/c/9dc0cad203ab
- [v2,net-next,2/6] sfc: bind indirect blocks for TC offload on EF100
https://git.kernel.org/netdev/net-next/c/5b2e12d51bd8
- [v2,net-next,3/6] sfc: optional logging of TC offload errors
https://git.kernel.org/netdev/net-next/c/7c9d266d8faf
- [v2,net-next,4/6] sfc: add a hashtable for offloaded TC rules
https://git.kernel.org/netdev/net-next/c/f54a28a21166
- [v2,net-next,5/6] sfc: interrogate MAE capabilities at probe time
https://git.kernel.org/netdev/net-next/c/7ce3e235f212
- [v2,net-next,6/6] sfc: bare bones TC offload on EF100
https://git.kernel.org/netdev/net-next/c/d902e1a737d4
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:[~2022-09-28 8:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-26 18:57 [PATCH v2 net-next 0/6] sfc: bare bones TC offload ecree
2022-09-26 18:57 ` [PATCH v2 net-next 1/6] sfc: bind blocks for TC offload on EF100 ecree
2022-09-28 8:43 ` Martin Habets
2022-09-26 18:57 ` [PATCH v2 net-next 2/6] sfc: bind indirect " ecree
2022-09-26 18:57 ` [PATCH v2 net-next 3/6] sfc: optional logging of TC offload errors ecree
2022-09-28 17:44 ` Jakub Kicinski
2022-09-28 18:17 ` Edward Cree
2022-09-28 18:32 ` Jakub Kicinski
2022-09-28 18:58 ` Edward Cree
2022-09-28 19:07 ` Jakub Kicinski
2022-09-28 21:14 ` Edward Cree
2022-09-29 1:15 ` Jakub Kicinski
2022-09-30 9:03 ` Edward Cree
2022-09-30 14:19 ` Jakub Kicinski
2022-10-03 19:30 ` Edward Cree
2022-09-26 18:57 ` [PATCH v2 net-next 4/6] sfc: add a hashtable for offloaded TC rules ecree
2022-09-26 18:57 ` [PATCH v2 net-next 5/6] sfc: interrogate MAE capabilities at probe time ecree
2022-09-26 18:57 ` [PATCH v2 net-next 6/6] sfc: bare bones TC offload on EF100 ecree
2022-09-28 8:50 ` 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=166435501724.19549.11910754562202475038.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=ecree.xilinx@gmail.com \
--cc=ecree@xilinx.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 \
/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).