On 9/28/20 10:04 PM, Oliver Hartkopp wrote:
> CAN Transport Protocols offer support for segmented Point-to-Point
> communication between CAN nodes via two defined CAN Identifiers.
> As CAN frames can only transport a small amount of data bytes
> (max. 8 bytes for 'classic' CAN and max. 64 bytes for CAN FD) this
> segmentation is needed to transport longer PDUs as needed e.g. for
> vehicle diagnosis (UDS, ISO 14229) or IP-over-CAN traffic.
> This protocol driver implements data transfers according to
> ISO 15765-2:2016 for 'classic' CAN and CAN FD frame types.
>
> Signed-off-by: Oliver Hartkopp <socketcan@xxxxxxxxxxxx>
Applied to linux-can-next with some changes:
> diff --git a/net/can/isotp.c b/net/can/isotp.c
> new file mode 100644
> index 000000000000..efed3e47b6ee
> --- /dev/null
> +++ b/net/can/isotp.c
> @@ -0,0 +1,1428 @@
> +// SPDX-License-Identifier: ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause)
Removed the syscall note, as it's only ment for header files. See:
d77cd7fefc0d can: remove "WITH Linux-syscall-note" fro
SPDX tag of C files
Further I've fixes some indention, a checkpatch warning and some typos.
regards,
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Embedded Linux | https://www.pengutronix.de |
Vertretung West/Dortmund | Phone: +49-231-2826-924 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
Attachment:
signature.asc
Description: OpenPGP digital signature
