From: patchwork-bot+netdevbpf@kernel.org
To: Jiri Pirko <jiri@resnulli.us>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
pabeni@redhat.com, edumazet@google.com,
michael.chan@broadcom.com, jesse.brandeburg@intel.com,
anthony.l.nguyen@intel.com, tariqt@nvidia.com, saeedm@nvidia.com,
leon@kernel.org, idosch@nvidia.com, petrm@nvidia.com,
simon.horman@corigine.com, aelior@marvell.com,
manishc@marvell.com, jacob.e.keller@intel.com, gal@nvidia.com,
yinjun.zhang@corigine.com, fei.qin@corigine.com,
Niklas.Cassel@wdc.com
Subject: Re: [patch net-next v2 00/12] devlink: Cleanup params usage
Date: Fri, 27 Jan 2023 12:50:19 +0000 [thread overview]
Message-ID: <167482381901.15666.2800630597243633345.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230126075838.1643665-1-jiri@resnulli.us>
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Thu, 26 Jan 2023 08:58:26 +0100 you wrote:
> From: Jiri Pirko <jiri@nvidia.com>
>
> This patchset takes care of small cleanup of devlink params usage.
> Some of the patches (first 2/3) are cosmetic, but I would like to
> point couple of interesting ones:
>
> Patch 9 is the main one of this set and introduces devlink instance
> locking for params, similar to other devlink objects. That allows params
> to be registered/unregistered when devlink instance is registered.
>
> [...]
Here is the summary with links:
- [net-next,v2,01/12] net/mlx5: Change devlink param register/unregister function names
https://git.kernel.org/netdev/net-next/c/c8aebff4599f
- [net-next,v2,02/12] net/mlx5: Covert devlink params registration to use devlink_params_register/unregister()
https://git.kernel.org/netdev/net-next/c/a756185ac3b9
- [net-next,v2,03/12] devlink: make devlink_param_register/unregister static
https://git.kernel.org/netdev/net-next/c/020dd127a3fe
- [net-next,v2,04/12] devlink: don't work with possible NULL pointer in devlink_param_unregister()
https://git.kernel.org/netdev/net-next/c/bb9bb6bfd1c3
- [net-next,v2,05/12] ice: remove pointless calls to devlink_param_driverinit_value_set()
https://git.kernel.org/netdev/net-next/c/2fc631b5d75d
- [net-next,v2,06/12] qed: remove pointless call to devlink_param_driverinit_value_set()
https://git.kernel.org/netdev/net-next/c/6fd6eda0e65d
- [net-next,v2,07/12] devlink: make devlink_param_driverinit_value_set() return void
https://git.kernel.org/netdev/net-next/c/85fe0b324c83
- [net-next,v2,08/12] devlink: put couple of WARN_ONs in devlink_param_driverinit_value_get()
https://git.kernel.org/netdev/net-next/c/3f716a620e13
- [net-next,v2,09/12] devlink: protect devlink param list by instance lock
https://git.kernel.org/netdev/net-next/c/075935f0ae0f
- [net-next,v2,10/12] net/mlx5: Move fw reset devlink param to fw reset code
https://git.kernel.org/netdev/net-next/c/c2077fbc42ae
- [net-next,v2,11/12] net/mlx5: Move flow steering devlink param to flow steering code
https://git.kernel.org/netdev/net-next/c/db492c1e5b1b
- [net-next,v2,12/12] net/mlx5: Move eswitch port metadata devlink param to flow eswitch code
https://git.kernel.org/netdev/net-next/c/d2a651ef18c0
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-01-27 12:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-26 7:58 [patch net-next v2 00/12] devlink: Cleanup params usage Jiri Pirko
2023-01-26 7:58 ` [patch net-next v2 01/12] net/mlx5: Change devlink param register/unregister function names Jiri Pirko
2023-01-26 7:58 ` [patch net-next v2 02/12] net/mlx5: Covert devlink params registration to use devlink_params_register/unregister() Jiri Pirko
2023-01-26 7:58 ` [patch net-next v2 03/12] devlink: make devlink_param_register/unregister static Jiri Pirko
2023-01-26 7:58 ` [patch net-next v2 04/12] devlink: don't work with possible NULL pointer in devlink_param_unregister() Jiri Pirko
2023-01-26 7:58 ` [patch net-next v2 05/12] ice: remove pointless calls to devlink_param_driverinit_value_set() Jiri Pirko
2023-01-26 7:58 ` [patch net-next v2 06/12] qed: remove pointless call " Jiri Pirko
2023-01-26 7:58 ` [patch net-next v2 07/12] devlink: make devlink_param_driverinit_value_set() return void Jiri Pirko
2023-01-26 7:58 ` [patch net-next v2 08/12] devlink: put couple of WARN_ONs in devlink_param_driverinit_value_get() Jiri Pirko
2023-01-26 7:58 ` [patch net-next v2 09/12] devlink: protect devlink param list by instance lock Jiri Pirko
2023-01-26 9:28 ` Ido Schimmel
2023-01-27 11:32 ` Simon Horman
2023-01-27 11:41 ` Simon Horman
2023-01-26 7:58 ` [patch net-next v2 10/12] net/mlx5: Move fw reset devlink param to fw reset code Jiri Pirko
2023-01-26 7:58 ` [patch net-next v2 11/12] net/mlx5: Move flow steering devlink param to flow steering code Jiri Pirko
2023-01-26 7:58 ` [patch net-next v2 12/12] net/mlx5: Move eswitch port metadata devlink param to flow eswitch code Jiri Pirko
2023-01-27 12: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=167482381901.15666.2800630597243633345.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Niklas.Cassel@wdc.com \
--cc=aelior@marvell.com \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fei.qin@corigine.com \
--cc=gal@nvidia.com \
--cc=idosch@nvidia.com \
--cc=jacob.e.keller@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=manishc@marvell.com \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--cc=saeedm@nvidia.com \
--cc=simon.horman@corigine.com \
--cc=tariqt@nvidia.com \
--cc=yinjun.zhang@corigine.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