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 0/5] Improve locking in the VCAP API
Date: Wed, 18 Jan 2023 14:40:17 +0000 [thread overview]
Message-ID: <167405281789.22945.18204552117628849446.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230117085544.591523-1-steen.hegelund@microchip.com>
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Tue, 17 Jan 2023 09:55:39 +0100 you wrote:
> This improves the VCAP cache and the VCAP rule list protection against
> access from different sources.
>
> The VCAP Admin lock protects the list of rules for the VCAP instance as
> well as the cache used for encoding and decoding rules.
>
> This series provides dedicated functions for accessing rule statistics,
> decoding rule content, verifying if a rule exists and getting a rule with
> the lock held, as well as ensuring the use of the lock when the list of
> rules or the cache is accessed.
>
> [...]
Here is the summary with links:
- [net-next,1/5] net: microchip: sparx5: Add support for rule count by cookie
https://git.kernel.org/netdev/net-next/c/27d293cceee5
- [net-next,2/5] net: microchip: sparx5: Add support to check for existing VCAP rule id
https://git.kernel.org/netdev/net-next/c/975d86acaec7
- [net-next,3/5] net: microchip: sparx5: Add VCAP admin locking in debugFS
https://git.kernel.org/netdev/net-next/c/9579e2c271b4
- [net-next,4/5] net: microchip: sparx5: Improve VCAP admin locking in the VCAP API
https://git.kernel.org/netdev/net-next/c/1972b6d927ac
- [net-next,5/5] net: microchip: sparx5: Add lock initialization to the KUNIT tests
https://git.kernel.org/netdev/net-next/c/595655e08174
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-18 14:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-17 8:55 [PATCH net-next 0/5] Improve locking in the VCAP API Steen Hegelund
2023-01-17 8:55 ` [PATCH net-next 1/5] net: microchip: sparx5: Add support for rule count by cookie Steen Hegelund
2023-01-17 8:55 ` [PATCH net-next 2/5] net: microchip: sparx5: Add support to check for existing VCAP rule id Steen Hegelund
2023-01-17 8:55 ` [PATCH net-next 3/5] net: microchip: sparx5: Add VCAP admin locking in debugFS Steen Hegelund
2023-01-17 8:55 ` [PATCH net-next 4/5] net: microchip: sparx5: Improve VCAP admin locking in the VCAP API Steen Hegelund
2023-01-17 8:55 ` [PATCH net-next 5/5] net: microchip: sparx5: Add lock initialization to the KUNIT tests Steen Hegelund
2023-01-18 14:40 ` 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=167405281789.22945.18204552117628849446.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;
as well as URLs for NNTP newsgroup(s).