Weekly net upstream? - Re: [PATCH] vxcan: fix Kconfig description stating no local echo provided
Oliver Hartkopp <[email protected]>
| Newsgroups | org.kernel.vger.linux-can |
|---|---|
| Message-ID | <[email protected]> |
Hallo Marc, I would be glad if you could upstream this patch together with the now sashiko-approved fixes for can-bcm and can-isotp: https://lore.kernel.org/linux-can/[email protected]/ https://lore.kernel.org/linux-can/[email protected]/ Those are at least the fixes I'm aware off. Best regards, Oliver ps. a later update of can-next would be nice too. On 19.06.26 11:34, Oliver Hartkopp wrote: > > > On 19.06.26 11:00, Alexander Hölzl wrote: >> The Kconfig description of the vxcan kernel module erroneously stated >> the the vxcan >> interface does not provide a local echo of sent can frames. However >> this behavior was >> changed in commit 259bdba and vxcan interfaces now provide a local echo. >> >> This patch changes the description of the vxcan module in the Kconfig >> to reflect this change. >> >> Signed-off-by: Alexander Hölzl <[email protected]> > > Acked-by: Oliver Hartkopp <[email protected]> > > Thanks Alex! > > Best regards, > Oliver > >> --- >> drivers/net/can/Kconfig | 7 ++----- >> 1 file changed, 2 insertions(+), 5 deletions(-) >> >> diff --git a/drivers/net/can/Kconfig b/drivers/net/can/Kconfig >> index e15e320db476..e68b5bcee3a2 100644 >> --- 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. >