From nobody Wed Apr 29 08:07:28 2026 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 754A8C43334 for ; Sat, 11 Jun 2022 17:12:18 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S237931AbiFKRMQ (ORCPT ); Sat, 11 Jun 2022 13:12:16 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:34436 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230379AbiFKRMP (ORCPT ); Sat, 11 Jun 2022 13:12:15 -0400 Received: from mail.enpas.org (zhong.enpas.org [IPv6:2a03:4000:2:537::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 865CC24F34; Sat, 11 Jun 2022 10:12:11 -0700 (PDT) Received: from [127.0.0.1] (localhost [127.0.0.1]) by mail.enpas.org (Postfix) with ESMTPSA id 5AD2E100022; Sat, 11 Jun 2022 17:12:10 +0000 (UTC) From: Max Staudt To: Wolfgang Grandegger , Marc Kleine-Budde Cc: linux-can@vger.kernel.org, Vincent Mailhol , linux-kernel@vger.kernel.org, Max Staudt Subject: [PATCH] can: Break loopback loop on loopback documentation Date: Sat, 11 Jun 2022 19:11:55 +0200 Message-Id: <20220611171155.9090-1-max@enpas.org> X-Mailer: git-send-email 2.30.2 MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Type: text/plain; charset="utf-8" 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 --- Documentation/networking/can.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/networking/can.rst b/Documentation/networking/ca= n.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 loop= back 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). =20 The loopback functionality is enabled by default to reflect standard networking behaviour for CAN applications. Due to some requests from --=20 2.30.2