X-Git-Url: http://pileus.org/git/?a=blobdiff_plain;f=Documentation%2Fnetworking%2Fcan.txt;h=0cbe6ec22d6ff1d6a3c739f05ae61f4dc24781ec;hb=15b04859a21358f8aec1c06b4604877d604b05ee;hp=f3089d4235153b6fa03aaf5c8d09c81043bba996;hpb=5c2740280fef1c2da7835dea3856b5e9fc2a4bfd;p=~andy%2Flinux

diff --git a/Documentation/networking/can.txt b/Documentation/networking/can.txt
index f3089d42351..0cbe6ec22d6 100644
--- a/Documentation/networking/can.txt
+++ b/Documentation/networking/can.txt
@@ -554,12 +554,6 @@ solution for a couple of reasons:
   not specified in the struct can_frame and therefore it is only valid in
   CANFD_MTU sized CAN FD frames.
 
-  As long as the payload length is <=8 the received CAN frames from CAN FD
-  capable CAN devices can be received and read by legacy sockets too. When
-  user-generated CAN FD frames have a payload length <=8 these can be send
-  by legacy CAN network interfaces too. Sending CAN FD frames with payload
-  length > 8 to a legacy CAN network interface returns an -EMSGSIZE error.
-
   Implementation hint for new CAN applications:
 
   To build a CAN FD aware application use struct canfd_frame as basic CAN