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/8] Add support for VCAP debugFS in Sparx5
Date: Mon, 21 Nov 2022 11:40:17 +0000 [thread overview]
Message-ID: <166903081706.14617.12205489004712356542.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221117213114.699375-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, 17 Nov 2022 22:31:06 +0100 you wrote:
> This provides support for getting VCAP instance, VCAP rule and VCAP port
> keyset configuration information via the debug file system.
>
> 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/
>
> [...]
Here is the summary with links:
- [net-next,v2,1/8] net: microchip: sparx5: Ensure L3 protocol has a default value
https://git.kernel.org/netdev/net-next/c/bcddc196d481
- [net-next,v2,2/8] net: microchip: sparx5: Ensure VCAP last_used_addr is set back to default
https://git.kernel.org/netdev/net-next/c/277e9179efe5
- [net-next,v2,3/8] net: microchip: sparx5: Add VCAP debugFS support
https://git.kernel.org/netdev/net-next/c/e0305cc1d125
- [net-next,v2,4/8] net: microchip: sparx5: Add raw VCAP debugFS support for the VCAP API
https://git.kernel.org/netdev/net-next/c/d4134d41e3cb
- [net-next,v2,5/8] net: microchip: sparx5: Add VCAP rule debugFS support for the VCAP API
https://git.kernel.org/netdev/net-next/c/3a7921560d2f
- [net-next,v2,6/8] net: microchip: sparx5: Add VCAP debugFS key/action support for the VCAP API
https://git.kernel.org/netdev/net-next/c/72d84dd609be
- [net-next,v2,7/8] net: microchip: sparx5: Add VCAP locking to protect rules
https://git.kernel.org/netdev/net-next/c/71c9de995260
- [net-next,v2,8/8] net: microchip: sparx5: Add VCAP debugfs KUNIT test
https://git.kernel.org/netdev/net-next/c/552b7d131aa0
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2022-11-21 11:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-17 21:31 [PATCH net-next v2 0/8] Add support for VCAP debugFS in Sparx5 Steen Hegelund
2022-11-17 21:31 ` [PATCH net-next v2 1/8] net: microchip: sparx5: Ensure L3 protocol has a default value Steen Hegelund
2022-11-17 21:31 ` [PATCH net-next v2 2/8] net: microchip: sparx5: Ensure VCAP last_used_addr is set back to default Steen Hegelund
2022-11-17 21:31 ` [PATCH net-next v2 3/8] net: microchip: sparx5: Add VCAP debugFS support Steen Hegelund
2022-11-17 21:31 ` [PATCH net-next v2 4/8] net: microchip: sparx5: Add raw VCAP debugFS support for the VCAP API Steen Hegelund
2022-11-17 21:31 ` [PATCH net-next v2 5/8] net: microchip: sparx5: Add VCAP rule " Steen Hegelund
2022-11-17 21:31 ` [PATCH net-next v2 6/8] net: microchip: sparx5: Add VCAP debugFS key/action " Steen Hegelund
2022-11-17 21:31 ` [PATCH net-next v2 7/8] net: microchip: sparx5: Add VCAP locking to protect rules Steen Hegelund
2022-11-17 21:31 ` [PATCH net-next v2 8/8] net: microchip: sparx5: Add VCAP debugfs KUNIT test Steen Hegelund
2022-11-21 11:40 ` patchwork-bot+netdevbpf [this message]
2022-11-21 19:01 ` [PATCH net-next v2 0/8] Add support for VCAP debugFS in Sparx5 Jakub Kicinski
2022-11-22 9:17 ` Steen Hegelund
2022-11-22 18:47 ` Jakub Kicinski
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=166903081706.14617.12205489004712356542.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;
as well as URLs for NNTP newsgroup(s).