diff options
author | Max Staudt <max@enpas.org> | 2022-06-11 20:11:55 +0300 |
---|---|---|
committer | Marc Kleine-Budde <mkl@pengutronix.de> | 2022-06-11 23:40:13 +0300 |
commit | a9cf02c6a671bc84a348cd5934627ff68d8d8d35 (patch) | |
tree | c9c08598a8fe1d73841562aacc90ed2b912a2402 /Documentation | |
parent | 6914df1891c27f83e538dab3f5aadd2842e89a7f (diff) |
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 <max@enpas.org>
Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
Diffstat (limited to 'Documentation')
-rw-r--r-- | Documentation/networking/can.rst | 2 |
1 files changed, 1 insertions, 1 deletions
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 |