Message ID | 20220823070213.1008956-1-jiri@resnulli.us (mailing list archive) |
---|---|
State | Accepted |
Commit | 77a70f9c5b8678218a51cf2ae39a52cb4b6bc16c |
Delegated to: | Netdev Maintainers |
Headers | show |
Series | [net-next] Documentation: devlink: fix the locking section | expand |
Hello: This patch was applied to netdev/net-next.git (master) by Jakub Kicinski <kuba@kernel.org>: On Tue, 23 Aug 2022 09:02:13 +0200 you wrote: > From: Jiri Pirko <jiri@nvidia.com> > > As all callbacks are converted now, fix the text reflecting that change. > > Suggested-by: Jakub Kicinski <kuba@kernel.org> > Signed-off-by: Jiri Pirko <jiri@nvidia.com> > > [...] Here is the summary with links: - [net-next] Documentation: devlink: fix the locking section https://git.kernel.org/netdev/net-next/c/77a70f9c5b86 You are awesome, thank you!
diff --git a/Documentation/networking/devlink/index.rst b/Documentation/networking/devlink/index.rst index e3a5f985673e..4b653d040627 100644 --- a/Documentation/networking/devlink/index.rst +++ b/Documentation/networking/devlink/index.rst @@ -13,10 +13,8 @@ new APIs prefixed by ``devl_*``. The older APIs handle all the locking in devlink core, but don't allow registration of most sub-objects once the main devlink object is itself registered. The newer ``devl_*`` APIs assume the devlink instance lock is already held. Drivers can take the instance -lock by calling ``devl_lock()``. It is also held in most of the callbacks. -Eventually all callbacks will be invoked under the devlink instance lock, -refer to the use of the ``DEVLINK_NL_FLAG_NO_LOCK`` flag in devlink core -to find out which callbacks are not converted, yet. +lock by calling ``devl_lock()``. It is also held all callbacks of devlink +netlink commands. Drivers are encouraged to use the devlink instance lock for their own needs.