can: vxcan: Kconfig: fix description stating no local echo provided

The Kconfig description of the vxcan kernel module erroneously states the
the vxcan interface does not provide a local echo of sent can frames.
However this behavior changed in commit 259bdba27e32 ("vxcan: enable local
echo for sent CAN frames") and vxcan interfaces now provide a local echo.

Change the description of the vxcan module in the Kconfig to reflect this
change.

Signed-off-by: Alexander Hölzl <alexander.hoelzl@gmx.net>
Acked-by: Oliver Hartkopp <socketcan@hartkopp.net>
Link: https://patch.msgid.link/20260619090035.17769-1-alexander.hoelzl@gmx.net
[mkl: rephrase patch description]
Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>

diff --git a/drivers/net/can/Kconfig b/drivers/net/can/Kconfig
index e4058708ae6833d48ea0626b0f9b00372f91c1ff..a8fad6fe530207ca7e97124c75c1c24c5169ed80 100644 (file)
--- a/drivers/net/can/Kconfig
+++ b/drivers/net/can/Kconfig
@@ -40,11 +40,8 @@ config CAN_VXCAN
          When one end receives the packet it appears on its pair and vice
          versa. The vxcan can be used for cross namespace communication.
 
-         In opposite to vcan loopback devices the vxcan only forwards CAN
-         frames to its pair and does *not* provide a local echo of sent
-         CAN frames. To disable a potential echo in af_can.c the vxcan driver
-         announces IFF_ECHO in the interface flags. To have a clean start
-         in each namespace the CAN GW hop counter is set to zero.
+         To have a clean start in each namespace the CAN GW hop counter is
+         set to zero.
 
          This driver can also be built as a module.  If so, the module
          will be called vxcan.