[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20220611171155.9090-1-max@enpas.org>
Date: Sat, 11 Jun 2022 19:11:55 +0200
From: Max Staudt <max@...as.org>
To: Wolfgang Grandegger <wg@...ndegger.com>,
Marc Kleine-Budde <mkl@...gutronix.de>
Cc: linux-can@...r.kernel.org,
Vincent Mailhol <vincent.mailhol@...il.com>,
linux-kernel@...r.kernel.org, Max Staudt <max@...as.org>
Subject: [PATCH] can: Break loopback loop on loopback documentation
There are two sections called "Local Loopback of Sent Frames".
One was meant to link to the other, but pointed at itself instead.
Signed-off-by: Max Staudt <max@...as.org>
---
Documentation/networking/can.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/networking/can.rst b/Documentation/networking/can.rst
index f34cb0e4460e..ebc822e605f5 100644
--- a/Documentation/networking/can.rst
+++ b/Documentation/networking/can.rst
@@ -168,7 +168,7 @@ reflect the correct [#f1]_ traffic on the node the loopback of the sent
data has to be performed right after a successful transmission. If
the CAN network interface is not capable of performing the loopback for
some reason the SocketCAN core can do this task as a fallback solution.
-See :ref:`socketcan-local-loopback1` for details (recommended).
+See :ref:`socketcan-local-loopback2` for details (recommended).
The loopback functionality is enabled by default to reflect standard
networking behaviour for CAN applications. Due to some requests from
--
2.30.2
Powered by blists - more mailing lists