public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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 v2 00/10] Adding Sparx5 ES0 VCAP support
Date: Thu, 16 Feb 2023 08:30:19 +0000	[thread overview]
Message-ID: <167653621907.28100.17908588254142053263.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230214104049.1553059-1-steen.hegelund@microchip.com>

Hello:

This series was applied to netdev/net-next.git (master)
by Paolo Abeni <pabeni@redhat.com>:

On Tue, 14 Feb 2023 11:40:39 +0100 you wrote:
> This provides the Egress Stage 0 (ES0) VCAP (Versatile Content-Aware
> Processor) support for the Sparx5 platform.
> 
> The ES0 VCAP is an Egress Access Control VCAP that uses frame keyfields and
> previously classified keyfields to add, rewrite or remove VLAN tags on the
> egress frames, and is therefore often referred to as the rewriter.
> 
> [...]

Here is the summary with links:
  - [net-next,v2,01/10] net: microchip: sparx5: Discard frames with SMAC multicast addresses
    https://git.kernel.org/netdev/net-next/c/65b6625069a4
  - [net-next,v2,02/10] net: microchip: sparx5: Clear rule counter even if lookup is disabled
    https://git.kernel.org/netdev/net-next/c/d7953da4f293
  - [net-next,v2,03/10] net: microchip: sparx5: Egress VLAN TPID configuration follows IFH
    https://git.kernel.org/netdev/net-next/c/38f6408c6071
  - [net-next,v2,04/10] net: microchip: sparx5: Use chain ids without offsets when enabling rules
    https://git.kernel.org/netdev/net-next/c/0518e914f34a
  - [net-next,v2,05/10] net: microchip: sparx5: Improve the error handling for linked rules
    https://git.kernel.org/netdev/net-next/c/b5b0c3645988
  - [net-next,v2,06/10] net: microchip: sparx5: Add ES0 VCAP model and updated KUNIT VCAP model
    https://git.kernel.org/netdev/net-next/c/a5cc98adf3cb
  - [net-next,v2,07/10] net: microchip: sparx5: Updated register interface with VCAP ES0 access
    https://git.kernel.org/netdev/net-next/c/f2a77dd69f51
  - [net-next,v2,08/10] net: microchip: sparx5: Add ES0 VCAP keyset configuration for Sparx5
    https://git.kernel.org/netdev/net-next/c/3cbe7537a7f1
  - [net-next,v2,09/10] net: microchip: sparx5: Add TC support for the ES0 VCAP
    https://git.kernel.org/netdev/net-next/c/52b28a93c45d
  - [net-next,v2,10/10] net: microchip: sparx5: Add TC vlan action support for the ES0 VCAP
    https://git.kernel.org/netdev/net-next/c/ebf44ded76e9

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-02-16  8:30 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-14 10:40 [PATCH net-next v2 00/10] Adding Sparx5 ES0 VCAP support Steen Hegelund
2023-02-14 10:40 ` [PATCH net-next v2 01/10] net: microchip: sparx5: Discard frames with SMAC multicast addresses Steen Hegelund
2023-02-14 10:40 ` [PATCH net-next v2 02/10] net: microchip: sparx5: Clear rule counter even if lookup is disabled Steen Hegelund
2023-02-14 10:40 ` [PATCH net-next v2 03/10] net: microchip: sparx5: Egress VLAN TPID configuration follows IFH Steen Hegelund
2023-02-14 10:40 ` [PATCH net-next v2 04/10] net: microchip: sparx5: Use chain ids without offsets when enabling rules Steen Hegelund
2023-02-14 10:40 ` [PATCH net-next v2 05/10] net: microchip: sparx5: Improve the error handling for linked rules Steen Hegelund
2023-02-14 10:40 ` [PATCH net-next v2 06/10] net: microchip: sparx5: Add ES0 VCAP model and updated KUNIT VCAP model Steen Hegelund
2023-02-16  8:09   ` Paolo Abeni
2023-02-16  9:07     ` Steen Hegelund
2023-02-16  9:38       ` Paolo Abeni
2023-02-14 10:40 ` [PATCH net-next v2 07/10] net: microchip: sparx5: Updated register interface with VCAP ES0 access Steen Hegelund
2023-02-14 10:40 ` [PATCH net-next v2 08/10] net: microchip: sparx5: Add ES0 VCAP keyset configuration for Sparx5 Steen Hegelund
2023-02-14 10:40 ` [PATCH net-next v2 09/10] net: microchip: sparx5: Add TC support for the ES0 VCAP Steen Hegelund
2023-02-14 10:40 ` [PATCH net-next v2 10/10] net: microchip: sparx5: Add TC vlan action " Steen Hegelund
2023-02-16  8: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=167653621907.28100.17908588254142053263.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