From: patchwork-bot+netdevbpf@kernel.org
To: Steen Hegelund <steen.hegelund@microchip.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, UNGLinuxDriver@microchip.com,
rdunlap@infradead.org, casper.casan@gmail.com,
rmk+kernel@armlinux.org.uk, wanjiabing@vivo.com,
nhuck@google.com, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Steen.Hegelund@microchip.com, daniel.machon@microchip.com,
horatiu.vultur@microchip.com, lars.povlsen@microchip.com,
error27@gmail.com, michael@walle.cc
Subject: Re: [PATCH net-next 0/8] Adding Sparx5 ES2 VCAP support
Date: Mon, 30 Jan 2023 07:40:18 +0000 [thread overview]
Message-ID: <167506441838.19672.6690813495078695286.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230127130830.1481526-1-steen.hegelund@microchip.com>
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Fri, 27 Jan 2023 14:08:22 +0100 you wrote:
> This provides the Egress Stage 2 (ES2) VCAP (Versatile Content-Aware
> Processor) support for the Sparx5 platform.
>
> The ES2 VCAP is an Egress Access Control VCAP that uses frame keyfields and
> previously classified keyfields to apply e.g. policing, trapping or
> mirroring to frames.
>
> [...]
Here is the summary with links:
- [net-next,1/8] net: microchip: sparx5: Add support for getting keysets without a type id
https://git.kernel.org/netdev/net-next/c/c02b19edc78d
- [net-next,2/8] net: microchip: sparx5: Improve the IP frame key match for IPv6 frames
https://git.kernel.org/netdev/net-next/c/4114ef2ce273
- [net-next,3/8] net: microchip: sparx5: Improve error message when parsing CVLAN filter
https://git.kernel.org/netdev/net-next/c/a5300724ce73
- [net-next,4/8] net: microchip: sparx5: Add ES2 VCAP model and updated KUNIT VCAP model
https://git.kernel.org/netdev/net-next/c/9d712b8ddbb4
- [net-next,5/8] net: microchip: sparx5: Add ES2 VCAP keyset configuration for Sparx5
https://git.kernel.org/netdev/net-next/c/b95d9e2c20c9
- [net-next,6/8] net: microchip: sparx5: Add ingress information to VCAP instance
https://git.kernel.org/netdev/net-next/c/e7e3f514713e
- [net-next,7/8] net: microchip: sparx5: Add TC support for the ES2 VCAP
https://git.kernel.org/netdev/net-next/c/7b911a5311b8
- [net-next,8/8] net: microchip: sparx5: Add KUNIT tests for enabling/disabling chains
https://git.kernel.org/netdev/net-next/c/1f741f001160
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-01-30 7:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-27 13:08 [PATCH net-next 0/8] Adding Sparx5 ES2 VCAP support Steen Hegelund
2023-01-27 13:08 ` [PATCH net-next 1/8] net: microchip: sparx5: Add support for getting keysets without a type id Steen Hegelund
2023-01-27 13:08 ` [PATCH net-next 2/8] net: microchip: sparx5: Improve the IP frame key match for IPv6 frames Steen Hegelund
2023-01-27 13:08 ` [PATCH net-next 3/8] net: microchip: sparx5: Improve error message when parsing CVLAN filter Steen Hegelund
2023-01-27 13:08 ` [PATCH net-next 4/8] net: microchip: sparx5: Add ES2 VCAP model and updated KUNIT VCAP model Steen Hegelund
2023-01-27 13:08 ` [PATCH net-next 5/8] net: microchip: sparx5: Add ES2 VCAP keyset configuration for Sparx5 Steen Hegelund
2023-01-27 13:08 ` [PATCH net-next 6/8] net: microchip: sparx5: Add ingress information to VCAP instance Steen Hegelund
2023-01-27 13:08 ` [PATCH net-next 7/8] net: microchip: sparx5: Add TC support for the ES2 VCAP Steen Hegelund
2023-01-27 13:08 ` [PATCH net-next 8/8] net: microchip: sparx5: Add KUNIT tests for enabling/disabling chains Steen Hegelund
2023-01-30 7:40 ` 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=167506441838.19672.6690813495078695286.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=UNGLinuxDriver@microchip.com \
--cc=casper.casan@gmail.com \
--cc=daniel.machon@microchip.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=error27@gmail.com \
--cc=horatiu.vultur@microchip.com \
--cc=kuba@kernel.org \
--cc=lars.povlsen@microchip.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@walle.cc \
--cc=netdev@vger.kernel.org \
--cc=nhuck@google.com \
--cc=pabeni@redhat.com \
--cc=rdunlap@infradead.org \
--cc=rmk+kernel@armlinux.org.uk \
--cc=steen.hegelund@microchip.com \
--cc=wanjiabing@vivo.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