Changes in Makefile

e057dd3f - can: add ISO 15765-2:2016 transport protocol

Mon, 28 Sep 2020 20:04:04 +0000

can: add ISO 15765-2:2016 transport protocolCAN Transport Protocols offer support for segmented Point-to-Pointcommunication 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) thissegmentation is needed to transport longer PDUs as needed e.g. forvehicle diagnosis (UDS, ISO 14229) or IP-over-CAN traffic.This protocol driver implements data transfers according toISO 15765-2:2016 for 'classic' CAN and CAN FD frame types.Signed-off-by: Oliver Hartkopp Link: https://lore.kernel.org/r/20200928200404.82229-1-socketcan@hartkopp.net[mkl: Removed "WITH Linux-syscall-note" from isotp.c. Fixed indention, a checkpatch warning and typos. Replaced __u{8,32} by u{8,32}. Removed always false (optlen < 0) check in isotp_setsockopt().]Signed-off-by: Marc Kleine-Budde List of files: /linux-6.15/net/can/Makefile

9d71dd0c - can: add support of SAE J1939 protocol

Mon, 08 Oct 2018 09:48:36 +0000

can: add support of SAE J1939 protocolSAE J1939 is the vehicle bus recommended practice used for communicationand diagnostics among vehicle components. Originating in the car andheavy-duty truck industry in the United States, it is now widely used inother parts of the world.J1939, ISO 11783 and NMEA 2000 all share the same high level protocol.SAE J1939 can be considered the replacement for the older SAE J1708 andSAE J1587 specifications.Acked-by: Oliver Hartkopp Signed-off-by: Bastian Stender Signed-off-by: Elenita Hinds Signed-off-by: kbuild test robot Signed-off-by: Kurt Van Dijck Signed-off-by: Maxime Jayat Signed-off-by: Robin van der Gracht Signed-off-by: Oleksij Rempel Signed-off-by: Marc Kleine-Budde List of files: /linux-6.15/net/can/Makefile

b2441318 - License cleanup: add SPDX GPL-2.0 license identifier to files with no license

Wed, 01 Nov 2017 14:07:57 +0000

License cleanup: add SPDX GPL-2.0 license identifier to files with no licenseMany source files in the tree are missing licensing information, whichmakes it harder for compliance tools to determine the correct license.By default all files without license information are under the defaultlicense of the kernel, which is GPL version 2.Update the files which contain no license information with the 'GPL-2.0'SPDX license identifier. The SPDX identifier is a legally bindingshorthand, which can be used instead of the full boiler plate text.This patch is based on work done by Thomas Gleixner and Kate Stewart andPhilippe Ombredanne.How this work was done:Patches were generated and checked against linux-4.14-rc6 for a subset ofthe use cases: - file had no licensing information it it. - file was a */uapi/* one with no licensing information in it, - file was a */uapi/* one with existing licensing information,Further patches will be generated in subsequent months to fix up caseswhere non-standard license headers were used, and references to licensehad to be inferred by heuristics based on keywords.The analysis to determine which SPDX License Identifier to be applied toa file was done in a spreadsheet of side by side results from of theoutput of two independent scanners (ScanCode & Windriver) producing SPDXtag:value files created by Philippe Ombredanne. Philippe prepared thebase worksheet, and did an initial spot review of a few 1000 files.The 4.13 kernel was the starting point of the analysis with 60,537 filesassessed. Kate Stewart did a file by file comparison of the scannerresults in the spreadsheet to determine which SPDX license identifier(s)to be applied to the file. She confirmed any determination that was notimmediately clear with lawyers working with the Linux Foundation.Criteria used to select files for SPDX license identifier tagging was: - Files considered eligible had to be source code files. - Make and config files were included as candidates if they contained >5 lines of source - File already had some variant of a license header in it (even if <5 lines).All documentation files were explicitly excluded.The following heuristics were used to determine which SPDX licenseidentifiers to apply. - when both scanners couldn't find any license traces, file was considered to have no license information in it, and the top level COPYING file license applied. For non */uapi/* files that summary was: SPDX license identifier # files ---------------------------------------------------|------- GPL-2.0 11139 and resulted in the first patch in this series. If that file was a */uapi/* path one, it was "GPL-2.0 WITH Linux-syscall-note" otherwise it was "GPL-2.0". Results of that was: SPDX license identifier # files ---------------------------------------------------|------- GPL-2.0 WITH Linux-syscall-note 930 and resulted in the second patch in this series. - if a file had some form of licensing information in it, and was one of the */uapi/* ones, it was denoted with the Linux-syscall-note if any GPL family license was found in the file or had no licensing in it (per prior point). Results summary: SPDX license identifier # files ---------------------------------------------------|------ GPL-2.0 WITH Linux-syscall-note 270 GPL-2.0+ WITH Linux-syscall-note 169 ((GPL-2.0 WITH Linux-syscall-note) OR BSD-2-Clause) 21 ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause) 17 LGPL-2.1+ WITH Linux-syscall-note 15 GPL-1.0+ WITH Linux-syscall-note 14 ((GPL-2.0+ WITH Linux-syscall-note) OR BSD-3-Clause) 5 LGPL-2.0+ WITH Linux-syscall-note 4 LGPL-2.1 WITH Linux-syscall-note 3 ((GPL-2.0 WITH Linux-syscall-note) OR MIT) 3 ((GPL-2.0 WITH Linux-syscall-note) AND MIT) 1 and that resulted in the third patch in this series. - when the two scanners agreed on the detected license(s), that became the concluded license(s). - when there was disagreement between the two scanners (one detected a license but the other didn't, or they both detected different licenses) a manual inspection of the file occurred. - In most cases a manual inspection of the information in the file resulted in a clear resolution of the license that should apply (and which scanner probably needed to revisit its heuristics). - When it was not immediately clear, the license identifier was confirmed with lawyers working with the Linux Foundation. - If there was any question as to the appropriate license identifier, the file was flagged for further research and to be revisited later in time.In total, over 70 hours of logged manual review was done on thespreadsheet to determine the SPDX license identifiers to apply to thesource files by Kate, Philippe, Thomas and, in some cases, confirmationby lawyers working with the Linux Foundation.Kate also obtained a third independent scan of the 4.13 code base fromFOSSology, and compared selected files where the other two scannersdisagreed against that SPDX file, to see if there was new insights. TheWindriver scanner is based on an older version of FOSSology in part, sothey are related.Thomas did random spot checks in about 500 files from the spreadsheetsfor the uapi headers and agreed with SPDX license identifier in thefiles he inspected. For the non-uapi files Thomas did random spot checksin about 15000 files.In initial set of patches against 4.14-rc6, 3 files were found to havecopy/paste license identifier errors, and have been fixed to reflect thecorrect identifier.Additionally Philippe spent 10 hours this week doing a detailed manualinspection and review of the 12,461 patched files from the initial patchversion early this week with: - a full scancode scan run, collecting the matched texts, detected license ids and scores - reviewing anything where there was a license detected (about 500+ files) to ensure that the applied SPDX license was correct - reviewing anything where there was no detection but the patch license was not GPL-2.0 WITH Linux-syscall-note to ensure that the applied SPDX license was correctThis produced a worksheet with 20 files needing minor correction. Thisworksheet was then exported into 3 different .csv files for thedifferent types of files to be modified.These .csv files were then reviewed by Greg. Thomas wrote a script toparse the csv files and add the proper SPDX tag to the file, in theformat that the file expected. This script was further refined by Gregbased on the output to detect more types of files automatically and todistinguish between header and source .c files (which need differentcomment types.) Finally Greg ran the script using the .csv files togenerate the patches.Reviewed-by: Kate Stewart Reviewed-by: Philippe Ombredanne Reviewed-by: Thomas Gleixner Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/net/can/Makefile

a20fadf8 - can: build proc support only if CONFIG_PROC_FS is activated

Mon, 23 May 2016 13:13:00 +0000

can: build proc support only if CONFIG_PROC_FS is activatedWhen building can subsystem with CONFIG_PROC_FS=n I detected some unusedvariables warning by using proc functions. In CAN the proc handling isnicely placed in one object file. This patch adds simple add adependency on CONFIG_PROC_FS for CAN's proc.o file and correspondingstatic inline no-op functions.Signed-off-by: Alexander Aring Acked-by: Oliver Hartkopp [mkl: provide static inline noops instead of using #ifdefs]Signed-off-by: Marc Kleine-Budde List of files: /linux-6.15/net/can/Makefile

c1aabdf3 - can-gw: add netlink based CAN routing

Thu, 01 Sep 2011 04:23:23 +0000

can-gw: add netlink based CAN routingThis patch adds a CAN Gateway/Router to route (and modify) CAN frames.It is based on the PF_CAN core infrastructure for msg filtering and msgsending and can optionally modify routed CAN frames on the fly.CAN frames can *only* be routed between CAN network interfaces (one hop).They can be modified with AND/OR/XOR/SET operations as configured by thenetlink configuration interface known e.g. from iptables. From the netlinkview this can-gw implements RTM_{NEW|DEL|GET}ROUTE for PF_CAN.The CAN specific userspace tool to manage CAN routing entries can be found inthe CAN utils http://svn.berlios.de/wsvn/socketcan/trunk/can-utils/cangw.cat the SocketCAN SVN on BerliOS.Signed-off-by: Oliver Hartkopp Signed-off-by: David S. Miller List of files: /linux-6.15/net/can/Makefile

bac14e01 - Net: can: Makefile: Remove deprecated kbuild goal definitions

Sun, 21 Nov 2010 15:03:14 +0000

Net: can: Makefile: Remove deprecated kbuild goal definitionsChanged Makefile to use -y instead of -objsbecause -objs is deprecated and not mentioned inDocumentation/kbuild/makefiles.txt.Signed-off-by: Tracey Dent Signed-off-by: David S. Miller List of files: /linux-6.15/net/can/Makefile

ffd980f9 - [CAN]: Add broadcast manager (bcm) protocol

Fri, 16 Nov 2007 23:53:52 +0000

[CAN]: Add broadcast manager (bcm) protocolThis patch adds the CAN broadcast manager (bcm) protocol.Signed-off-by: Oliver Hartkopp Signed-off-by: Urs Thuermann Signed-off-by: David S. Miller List of files: /linux-6.15/net/can/Makefile

c18ce101 - [CAN]: Add raw protocol

Fri, 16 Nov 2007 23:53:09 +0000

[CAN]: Add raw protocolThis patch adds the CAN raw protocol.Signed-off-by: Oliver Hartkopp Signed-off-by: Urs Thuermann Signed-off-by: David S. Miller List of files: /linux-6.15/net/can/Makefile

0d66548a - [CAN]: Add PF_CAN core module

Fri, 16 Nov 2007 23:52:17 +0000

[CAN]: Add PF_CAN core moduleThis patch adds the CAN core functionality but no protocols or drivers.No protocol implementations are included here. They come as separatepatches. Protocol numbers are already in include/linux/can.h.Signed-off-by: Oliver Hartkopp Signed-off-by: Urs Thuermann Signed-off-by: David S. Miller List of files: /linux-6.15/net/can/Makefile