From: Max Staudt Date: Sat, 11 Jun 2022 17:11:55 +0000 (+0200) Subject: can: Break loopback loop on loopback documentation X-Git-Tag: v6.6.17~6916^2~282^2~4 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=a9cf02c6a671bc84a348cd5934627ff68d8d8d35;p=platform%2Fkernel%2Flinux-rpi.git 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. Link: https://lore.kernel.org/all/20220611171155.9090-1-max@enpas.org Fixes: 7d5977394515 ("can: migrate documentation to restructured text") Signed-off-by: Max Staudt Signed-off-by: Marc Kleine-Budde --- diff --git a/Documentation/networking/can.rst b/Documentation/networking/can.rst index f34cb0e..ebc822e 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