From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
pabeni@redhat.com, dsahern@kernel.org,
steffen.klassert@secunet.com, jreuter@yaina.de,
razor@blackwall.org, jiri@resnulli.us, kgraul@linux.ibm.com,
ivecera@redhat.com, jmaloy@redhat.com, ying.xue@windriver.com,
lucien.xin@gmail.com, arnd@arndb.de, yajun.deng@linux.dev,
atenart@kernel.org, richardsonnick@google.com,
hkallweit1@gmail.com, linux-hams@vger.kernel.org,
dev@openvswitch.org, linux-s390@vger.kernel.org,
tipc-discussion@lists.sourceforge.net
Subject: Re: [PATCH net-next] net: rename reference+tracking helpers
Date: Fri, 10 Jun 2022 05:40:16 +0000 [thread overview]
Message-ID: <165483961628.13976.4015696054691394649.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220608043955.919359-1-kuba@kernel.org>
Hello:
This patch was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 7 Jun 2022 21:39:55 -0700 you wrote:
> Netdev reference helpers have a dev_ prefix for historic
> reasons. Renaming the old helpers would be too much churn
> but we can rename the tracking ones which are relatively
> recent and should be the default for new code.
>
> Rename:
> dev_hold_track() -> netdev_hold()
> dev_put_track() -> netdev_put()
> dev_replace_track() -> netdev_ref_replace()
>
> [...]
Here is the summary with links:
- [net-next] net: rename reference+tracking helpers
https://git.kernel.org/netdev/net-next/c/d62607c3fe45
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-06-10 5:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-08 4:39 [PATCH net-next] net: rename reference+tracking helpers Jakub Kicinski
2022-06-08 8:27 ` Jiri Pirko
2022-06-08 14:58 ` Jakub Kicinski
2022-06-08 22:58 ` David Ahern
2022-06-08 23:00 ` Eric Dumazet
2022-06-09 11:49 ` Paolo Abeni
2022-06-09 13:53 ` Eric Dumazet
2022-06-09 3:29 ` Jakub Kicinski
2022-06-09 4:40 ` Jiri Pirko
2022-06-10 5: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=165483961628.13976.4015696054691394649.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=arnd@arndb.de \
--cc=atenart@kernel.org \
--cc=davem@davemloft.net \
--cc=dev@openvswitch.org \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=ivecera@redhat.com \
--cc=jiri@resnulli.us \
--cc=jmaloy@redhat.com \
--cc=jreuter@yaina.de \
--cc=kgraul@linux.ibm.com \
--cc=kuba@kernel.org \
--cc=linux-hams@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=lucien.xin@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=razor@blackwall.org \
--cc=richardsonnick@google.com \
--cc=steffen.klassert@secunet.com \
--cc=tipc-discussion@lists.sourceforge.net \
--cc=yajun.deng@linux.dev \
--cc=ying.xue@windriver.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