From: patchwork-bot+netdevbpf@kernel.org
To: Saeed Mahameed <saeed@kernel.org>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
edumazet@google.com, saeedm@nvidia.com, netdev@vger.kernel.org
Subject: Re: [PATCH net-next 0/9] mlx5 devlink mutex removal part 1
Date: Tue, 12 Jul 2022 08:50:15 +0000 [thread overview]
Message-ID: <165761581584.31192.16421025749968041368.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220711081408.69452-1-saeed@kernel.org>
Hello:
This series was applied to netdev/net-next.git (master)
by Paolo Abeni <pabeni@redhat.com>:
On Mon, 11 Jul 2022 01:13:59 -0700 you wrote:
> From: Saeed Mahameed <saeedm@nvidia.com>
>
> Moshe Shemesh Says:
> ===================
> 1) Fix devlink lock in mlx5 devlink eswitch callbacks
>
> Following the commit 14e426bf1a4d "devlink: hold the instance lock
> during eswitch_mode callbacks" which takes devlink instance lock for all
> devlink eswitch callbacks and adds a temporary workaround, this patchset
> removes the workaround, replaces devlink API functions by devl_ API
> where called from mlx5 driver eswitch callbacks flows and adds devlink
> instance lock in other driver's path that leads to these functions.
> While moving to devl_ API the patchset removes part of the devlink API
> functions which mlx5 was the last one to use and so not used by any
> driver now.
>
> [...]
Here is the summary with links:
- [net-next,1/9] net/mlx5: Remove devl_unlock from mlx5_eswtich_mode_callback_enter
https://git.kernel.org/netdev/net-next/c/367dfa121205
- [net-next,2/9] net/mlx5: Use devl_ API for rate nodes destroy
https://git.kernel.org/netdev/net-next/c/03f9c47d0f79
- [net-next,3/9] devlink: Remove unused function devlink_rate_nodes_destroy
https://git.kernel.org/netdev/net-next/c/868232f5cd38
- [net-next,4/9] net/mlx5: Use devl_ API in mlx5_esw_offloads_devlink_port_register
https://git.kernel.org/netdev/net-next/c/f1bc646c9a06
- [net-next,5/9] net/mlx5: Use devl_ API in mlx5_esw_devlink_sf_port_register
https://git.kernel.org/netdev/net-next/c/da212bd29d7f
- [net-next,6/9] devlink: Remove unused functions devlink_rate_leaf_create/destroy
https://git.kernel.org/netdev/net-next/c/df539fc62b06
- [net-next,7/9] net/mlx5: Use devl_ API in mlx5e_devlink_port_register
https://git.kernel.org/netdev/net-next/c/7b19119f4c7d
- [net-next,8/9] net/mlx5: Remove devl_unlock from mlx5_devlink_eswitch_mode_set
https://git.kernel.org/netdev/net-next/c/973598d46ede
- [net-next,9/9] devlink: Hold the instance lock in port_new / port_del callbacks
https://git.kernel.org/netdev/net-next/c/f0680ef0f949
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-07-12 8:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-11 8:13 [PATCH net-next 0/9] mlx5 devlink mutex removal part 1 Saeed Mahameed
2022-07-11 8:14 ` [PATCH net-next 1/9] net/mlx5: Remove devl_unlock from mlx5_eswtich_mode_callback_enter Saeed Mahameed
2022-07-11 8:14 ` [PATCH net-next 2/9] net/mlx5: Use devl_ API for rate nodes destroy Saeed Mahameed
2022-07-11 8:14 ` [PATCH net-next 3/9] devlink: Remove unused function devlink_rate_nodes_destroy Saeed Mahameed
2022-07-11 8:14 ` [PATCH net-next 4/9] net/mlx5: Use devl_ API in mlx5_esw_offloads_devlink_port_register Saeed Mahameed
2022-07-11 8:14 ` [PATCH net-next 5/9] net/mlx5: Use devl_ API in mlx5_esw_devlink_sf_port_register Saeed Mahameed
2022-07-11 8:14 ` [PATCH net-next 6/9] devlink: Remove unused functions devlink_rate_leaf_create/destroy Saeed Mahameed
2022-07-11 8:14 ` [PATCH net-next 7/9] net/mlx5: Use devl_ API in mlx5e_devlink_port_register Saeed Mahameed
2022-07-11 8:14 ` [PATCH net-next 8/9] net/mlx5: Remove devl_unlock from mlx5_devlink_eswitch_mode_set Saeed Mahameed
2022-07-11 8:14 ` [PATCH net-next 9/9] devlink: Hold the instance lock in port_new / port_del callbacks Saeed Mahameed
2022-07-12 3:03 ` [PATCH net-next 0/9] mlx5 devlink mutex removal part 1 Jakub Kicinski
2022-07-12 8:50 ` 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=165761581584.31192.16421025749968041368.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeed@kernel.org \
--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 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.