From 393acb51d048087ca82a66ecfd6449575a7eb2db Mon Sep 17 00:00:00 2001 From: Cosmin Ratiu Date: Sun, 11 Oct 2026 12:07:39 +0300 Subject: [PATCH] devlink: Fix accidental rebase error in nested devlink docs The referenced "Fixes" commit accidentally reverted a correction introduced in commit [1]. Revert that mistake. [1] commit e504cf18ef47 ("docs: net: fix minor issues with devlink docs") Fixes: 3bf4c5970ca8 ("devlink: Update nested instance locking comment") Signed-off-by: Cosmin Ratiu Signed-off-by: Tariq Toukan Reviewed-by: Joe Damato Link: https://patch.msgid.link/20261011090739.746757-1-tariqt@nvidia.com Signed-off-by: Jakub Kicinski --- Documentation/networking/devlink/index.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Documentation/networking/devlink/index.rst b/Documentation/networking/devlink/index.rst index 1af780c811ee..03f49389a755 100644 --- a/Documentation/networking/devlink/index.rst +++ b/Documentation/networking/devlink/index.rst @@ -33,8 +33,8 @@ sure to respect following rules: lock of both nested and parent instances at the same time, devlink instance lock of the nested instance should be taken first, only then instance lock of the parent instance could be taken. - - Driver should use object-specific helpers to setup the - nested relationship: + - Driver should use object-specific helpers to setup the nested relationship + before registering the nested devlink instance: - ``devl_nested_devlink_set()`` - called to setup devlink -> nested devlink relationship (could be used for multiple nested instances). -- knotmirror 0.0.1