From: patchwork-bot+netdevbpf@kernel.org
To: Pedro Tammela <pctammela@mojatatu.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
jiri@resnulli.us, jhs@mojatatu.com, victor@mojatatu.com,
martin@strongswan.org, idosch@nvidia.com, razor@blackwall.org,
lucien.xin@gmail.com, edwin.peer@broadcom.com,
amcohen@nvidia.com
Subject: Re: [PATCH net-next 0/2] net: rtnl: introduce rcu_replace_pointer_rtnl
Date: Mon, 18 Dec 2023 02:11:44 +0000 [thread overview]
Message-ID: <170286550432.14308.2113369674273572192.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231215175711.323784-1-pctammela@mojatatu.com>
Hello:
This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Fri, 15 Dec 2023 14:57:09 -0300 you wrote:
> Introduce the rcu_replace_pointer_rtnl helper to lockdep check rtnl lock
> rcu replacements, alongside the already existing helpers.
>
> Patch 2 uses the new helper in the rtnl_unregister_* functions.
>
> Originally this change was part of the P4TC series, as it's a recurrent
> pattern there, but since it has a use case in mainline we are pushing it
> separately.
>
> [...]
Here is the summary with links:
- [net-next,1/2] net: rtnl: introduce rcu_replace_pointer_rtnl
https://git.kernel.org/netdev/net-next/c/32da0f00ddcb
- [net-next,2/2] net: rtnl: use rcu_replace_pointer_rtnl in rtnl_unregister_*
https://git.kernel.org/netdev/net-next/c/174523479aae
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-12-18 2:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-15 17:57 [PATCH net-next 0/2] net: rtnl: introduce rcu_replace_pointer_rtnl Pedro Tammela
2023-12-15 17:57 ` [PATCH net-next 1/2] " Pedro Tammela
2023-12-17 12:17 ` Ido Schimmel
2023-12-17 14:19 ` Nikolay Aleksandrov
2023-12-15 17:57 ` [PATCH net-next 2/2] net: rtnl: use rcu_replace_pointer_rtnl in rtnl_unregister_* Pedro Tammela
2023-12-17 12:18 ` Ido Schimmel
2023-12-17 14:19 ` Nikolay Aleksandrov
2023-12-18 2:11 ` 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=170286550432.14308.2113369674273572192.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=amcohen@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=edwin.peer@broadcom.com \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=lucien.xin@gmail.com \
--cc=martin@strongswan.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pctammela@mojatatu.com \
--cc=razor@blackwall.org \
--cc=victor@mojatatu.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).