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
Subject: Re: [PATCH net-next v3 0/9] Add support for Sparx5 IS2 VCAP
Date: Mon, 24 Oct 2022 10:30:19 +0000 [thread overview]
Message-ID: <166660741961.18313.1095799162478409748.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221020130904.1215072-1-steen.hegelund@microchip.com>
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Thu, 20 Oct 2022 15:08:55 +0200 you wrote:
> This provides initial support for the Sparx5 VCAP functionality via the
> 'tc' traffic control userspace tool and its flower filter.
>
> Overview:
> =========
>
> The supported flower filter keys and actions are:
>
> [...]
Here is the summary with links:
- [net-next,v3,1/9] net: microchip: sparx5: Adding initial VCAP API support
https://git.kernel.org/netdev/net-next/c/8beef08f4618
- [net-next,v3,2/9] net: microchip: sparx5: Adding IS2 VCAP model to VCAP API
https://git.kernel.org/netdev/net-next/c/e8145e0685be
- [net-next,v3,3/9] net: microchip: sparx5: Adding IS2 VCAP register interface
https://git.kernel.org/netdev/net-next/c/45c00ad0030c
- [net-next,v3,4/9] net: microchip: sparx5: Adding initial tc flower support for VCAP API
https://git.kernel.org/netdev/net-next/c/c9da1ac1c212
- [net-next,v3,5/9] net: microchip: sparx5: Adding port keyset config and callback interface
https://git.kernel.org/netdev/net-next/c/46be056ee0fc
- [net-next,v3,6/9] net: microchip: sparx5: Adding basic rule management in VCAP API
https://git.kernel.org/netdev/net-next/c/8e10490b0064
- [net-next,v3,7/9] net: microchip: sparx5: Writing rules to the IS2 VCAP
https://git.kernel.org/netdev/net-next/c/683e05c03275
- [net-next,v3,8/9] net: microchip: sparx5: Adding KUNIT test VCAP model
https://git.kernel.org/netdev/net-next/c/5d7e5b0401d7
- [net-next,v3,9/9] net: microchip: sparx5: Adding KUNIT test for the VCAP API
https://git.kernel.org/netdev/net-next/c/67d637516fa9
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-10-24 10:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 13:08 [PATCH net-next v3 0/9] Add support for Sparx5 IS2 VCAP Steen Hegelund
2022-10-20 13:08 ` [PATCH net-next v3 1/9] net: microchip: sparx5: Adding initial VCAP API support Steen Hegelund
2022-10-20 13:08 ` [PATCH net-next v3 2/9] net: microchip: sparx5: Adding IS2 VCAP model to VCAP API Steen Hegelund
2022-10-20 13:08 ` [PATCH net-next v3 3/9] net: microchip: sparx5: Adding IS2 VCAP register interface Steen Hegelund
2022-10-20 13:08 ` [PATCH net-next v3 4/9] net: microchip: sparx5: Adding initial tc flower support for VCAP API Steen Hegelund
2022-10-20 13:09 ` [PATCH net-next v3 5/9] net: microchip: sparx5: Adding port keyset config and callback interface Steen Hegelund
2022-10-20 13:09 ` [PATCH net-next v3 6/9] net: microchip: sparx5: Adding basic rule management in VCAP API Steen Hegelund
2022-10-20 13:09 ` [PATCH net-next v3 7/9] net: microchip: sparx5: Writing rules to the IS2 VCAP Steen Hegelund
2022-10-20 13:09 ` [PATCH net-next v3 8/9] net: microchip: sparx5: Adding KUNIT test VCAP model Steen Hegelund
2022-10-20 13:09 ` [PATCH net-next v3 9/9] net: microchip: sparx5: Adding KUNIT test for the VCAP API Steen Hegelund
2022-10-24 10: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=166660741961.18313.1095799162478409748.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=UNGLinuxDriver@microchip.com \
--cc=casper.casan@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).