From: patchwork-bot+netdevbpf@kernel.org
To: Jiri Pirko <jiri@resnulli.us>
Cc: netdev@vger.kernel.org, kuba@kernel.org, pabeni@redhat.com,
davem@davemloft.net, edumazet@google.com, leon@kernel.org,
saeedm@nvidia.com, moshe@nvidia.com
Subject: Re: [patch net-next 0/3] devlink: small port_new/del() cleanup
Date: Wed, 24 May 2023 09:40:20 +0000 [thread overview]
Message-ID: <168492122056.15562.1210635654819470935.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230523123801.2007784-1-jiri@resnulli.us>
Hello:
This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Tue, 23 May 2023 14:37:58 +0200 you wrote:
> From: Jiri Pirko <jiri@nvidia.com>
>
> This patchset cleans up couple of leftovers after recent devlink locking
> changes. Previously, both port_new/dev() commands were called without
> holding instance lock. Currently all devlink commands are called with
> instance lock held.
>
> [...]
Here is the summary with links:
- [net-next,1/3] devlink: remove duplicate port notification
https://git.kernel.org/netdev/net-next/c/c496daeb8630
- [net-next,2/3] devlink: remove no longer true locking comment from port_new/del()
https://git.kernel.org/netdev/net-next/c/1bb1b5789850
- [net-next,3/3] devlink: pass devlink_port pointer to ops->port_del() instead of index
https://git.kernel.org/netdev/net-next/c/9277649c66fe
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-05-24 9:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-23 12:37 [patch net-next 0/3] devlink: small port_new/del() cleanup Jiri Pirko
2023-05-23 12:37 ` [patch net-next 1/3] devlink: remove duplicate port notification Jiri Pirko
2023-05-23 14:18 ` Simon Horman
2023-05-23 12:38 ` [patch net-next 2/3] devlink: remove no longer true locking comment from port_new/del() Jiri Pirko
2023-05-23 14:19 ` Simon Horman
2023-05-23 12:38 ` [patch net-next 3/3] devlink: pass devlink_port pointer to ops->port_del() instead of index Jiri Pirko
2023-05-23 14:19 ` Simon Horman
2023-05-24 4:15 ` [patch net-next 0/3] devlink: small port_new/del() cleanup Jakub Kicinski
2023-05-24 9: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=168492122056.15562.1210635654819470935.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=moshe@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeedm@nvidia.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).