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 v4 0/8] Add support for two classes of VCAP rules
Date: Mon, 16 Jan 2023 13:50:18 +0000 [thread overview]
Message-ID: <167387701842.13526.15302586636454079420.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230114134242.3737446-1-steen.hegelund@microchip.com>
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Sat, 14 Jan 2023 14:42:34 +0100 you wrote:
> This adds support for two classes of VCAP rules:
>
> - Permanent rules (added e.g. for PTP support)
> - TC user rules (added by the TC userspace tool)
>
> For this to work the VCAP Loopups must be enabled from boot, so that the
> "internal" clients like PTP can add rules that are always active.
>
> [...]
Here is the summary with links:
- [net-next,v4,1/8] net: microchip: vcap api: Erase VCAP cache before encoding rule
https://git.kernel.org/netdev/net-next/c/6573f71ae72f
- [net-next,v4,2/8] net: microchip: sparx5: Reset VCAP counter for new rules
https://git.kernel.org/netdev/net-next/c/95fa74148daa
- [net-next,v4,3/8] net: microchip: vcap api: Always enable VCAP lookups
https://git.kernel.org/netdev/net-next/c/01ef75a257fa
- [net-next,v4,4/8] net: microchip: vcap api: Convert multi-word keys/actions when encoding
https://git.kernel.org/netdev/net-next/c/33e3a273fd4f
- [net-next,v4,5/8] net: microchip: vcap api: Use src and dst chain id to chain VCAP lookups
https://git.kernel.org/netdev/net-next/c/cfd9e7b74a1e
- [net-next,v4,6/8] net: microchip: vcap api: Check chains when adding a tc flower filter
https://git.kernel.org/netdev/net-next/c/784c3067d094
- [net-next,v4,7/8] net: microchip: vcap api: Add a storage state to a VCAP rule
https://git.kernel.org/netdev/net-next/c/814e7693207f
- [net-next,v4,8/8] net: microchip: vcap api: Enable/Disable rules via chains in VCAP HW
https://git.kernel.org/netdev/net-next/c/18a15c769d4a
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-16 13:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-14 13:42 [PATCH net-next v4 0/8] Add support for two classes of VCAP rules Steen Hegelund
2023-01-14 13:42 ` [PATCH net-next v4 1/8] net: microchip: vcap api: Erase VCAP cache before encoding rule Steen Hegelund
2023-01-14 13:42 ` [PATCH net-next v4 2/8] net: microchip: sparx5: Reset VCAP counter for new rules Steen Hegelund
2023-01-14 13:42 ` [PATCH net-next v4 3/8] net: microchip: vcap api: Always enable VCAP lookups Steen Hegelund
2023-01-14 13:42 ` [PATCH net-next v4 4/8] net: microchip: vcap api: Convert multi-word keys/actions when encoding Steen Hegelund
2023-01-14 13:42 ` [PATCH net-next v4 5/8] net: microchip: vcap api: Use src and dst chain id to chain VCAP lookups Steen Hegelund
2023-01-14 13:42 ` [PATCH net-next v4 6/8] net: microchip: vcap api: Check chains when adding a tc flower filter Steen Hegelund
2023-01-14 13:42 ` [PATCH net-next v4 7/8] net: microchip: vcap api: Add a storage state to a VCAP rule Steen Hegelund
2023-01-14 13:42 ` [PATCH net-next v4 8/8] net: microchip: vcap api: Enable/Disable rules via chains in VCAP HW Steen Hegelund
2023-01-16 13: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=167387701842.13526.15302586636454079420.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