From: patchwork-bot+netdevbpf@kernel.org
To: Johannes Berg <johannes@sipsolutions.net>
Cc: netdev@vger.kernel.org, jiri@resnulli.us, jhs@mojatatu.com,
victor@mojatatu.com, kuba@kernel.org, pctammela@mojatatu.com,
martin@strongswan.org, horms@kernel.org, johannes.berg@intel.com
Subject: Re: [PATCH net-next v2 1/2] rtnetlink: add guard for RTNL
Date: Wed, 03 Apr 2024 09:00:28 +0000 [thread overview]
Message-ID: <171213482822.8514.9847706746678108403.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240328082748.b6003379b15b.I9da87266ad39fff647828b5822e6ac8898857b71@changeid>
Hello:
This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Thu, 28 Mar 2024 08:27:49 +0100 you wrote:
> From: Johannes Berg <johannes.berg@intel.com>
>
> The new guard/scoped_gard can be useful for the RTNL as well,
> so add a guard definition for it. It gets used like
>
> {
> guard(rtnl)();
> // RTNL held until end of block
> }
>
> [...]
Here is the summary with links:
- [net-next,v2,1/2] rtnetlink: add guard for RTNL
https://git.kernel.org/netdev/net-next/c/464eb03c4a7c
- [net-next,v2,2/2] netdevice: add DEFINE_FREE() for dev_put
https://git.kernel.org/netdev/net-next/c/b1f81b9a535b
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:[~2024-04-03 9:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-28 7:27 [PATCH net-next v2 1/2] rtnetlink: add guard for RTNL Johannes Berg
2024-03-28 7:27 ` [PATCH net-next v2 2/2] netdevice: add DEFINE_FREE() for dev_put Johannes Berg
2024-04-02 8:28 ` Simon Horman
2024-04-02 8:27 ` [PATCH net-next v2 1/2] rtnetlink: add guard for RTNL Simon Horman
2024-04-02 12:31 ` Jiri Pirko
2024-04-02 15:04 ` Jakub Kicinski
2024-04-03 9:00 ` 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=171213482822.8514.9847706746678108403.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=horms@kernel.org \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=johannes.berg@intel.com \
--cc=johannes@sipsolutions.net \
--cc=kuba@kernel.org \
--cc=martin@strongswan.org \
--cc=netdev@vger.kernel.org \
--cc=pctammela@mojatatu.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.