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
Subject: Re: [PATCH net-next v2 0/4] TC protocol all support in Sparx5 IS2 VCAP
Date: Fri, 25 Nov 2022 09:50:16 +0000 [thread overview]
Message-ID: <166936981682.9141.14094692376950850067.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221123152545.1997266-1-steen.hegelund@microchip.com>
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Wed, 23 Nov 2022 16:25:41 +0100 you wrote:
> This provides support for the TC flower filters 'protocol all' clause in
> the Sparx5 IS2 VCAP.
>
> It builds on top of the initial IS2 VCAP support found in these series:
>
> https://lore.kernel.org/all/20221020130904.1215072-1-steen.hegelund@microchip.com/
> https://lore.kernel.org/all/20221109114116.3612477-1-steen.hegelund@microchip.com/
> https://lore.kernel.org/all/20221111130519.1459549-1-steen.hegelund@microchip.com/
> https://lore.kernel.org/all/20221117213114.699375-1-steen.hegelund@microchip.com/
>
> [...]
Here is the summary with links:
- [net-next,v2,1/4] net: microchip: sparx5: Support for copying and modifying rules in the API
https://git.kernel.org/netdev/net-next/c/465a38a269e9
- [net-next,v2,2/4] net: microchip: sparx5: Support for TC protocol all
https://git.kernel.org/netdev/net-next/c/0ca609484877
- [net-next,v2,3/4] net: microchip: sparx5: Support for displaying a list of keysets
https://git.kernel.org/netdev/net-next/c/14b639caa6e4
- [net-next,v2,4/4] net: microchip: sparx5: Add VCAP filter keys KUNIT test
https://git.kernel.org/netdev/net-next/c/22f3c3257288
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-11-25 9:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-23 15:25 [PATCH net-next v2 0/4] TC protocol all support in Sparx5 IS2 VCAP Steen Hegelund
2022-11-23 15:25 ` [PATCH net-next v2 1/4] net: microchip: sparx5: Support for copying and modifying rules in the API Steen Hegelund
2022-11-23 15:25 ` [PATCH net-next v2 2/4] net: microchip: sparx5: Support for TC protocol all Steen Hegelund
2022-11-23 15:25 ` [PATCH net-next v2 3/4] net: microchip: sparx5: Support for displaying a list of keysets Steen Hegelund
2022-11-23 15:25 ` [PATCH net-next v2 4/4] net: microchip: sparx5: Add VCAP filter keys KUNIT test Steen Hegelund
2022-11-25 9: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=166936981682.9141.14094692376950850067.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=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=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