Changes in Makefile

ca75bcf0 - net: remove the caif_hsi driver

Thu, 01 Jul 2021 08:15:09 +0000

net: remove the caif_hsi driverThe caif_hsi driver relies on a cfhsi_get_ops symbol using symbol_get,but this symbol is not provided anywhere in the kernel tree. Removethis driver given that it is dead code.Signed-off-by: Christoph Hellwig Reviewed-by: Greg Kroah-Hartman Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/net/caif/Makefile

f2bf88c4 - net: caif: Remove unused caif SPI driver

Tue, 29 Sep 2020 20:25:11 +0000

net: caif: Remove unused caif SPI driverWhile chasing in_interrupt() (ab)use in drivers it turned out that thecaif_spi driver has never been in use since the driver was merged 10 yearsago. There never was any matching code which provides a platform device.The driver has not seen any update (asided of treewide changes andcleanups) since 8 years and the maintainers vanished from the planet.So analysing the potential contexts and the (in)correctness ofin_interrupt() usage is just a pointless exercise.Remove the cruft.Signed-off-by: Thomas Gleixner Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/net/caif/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/drivers/net/caif/Makefile

0d2e1a29 - caif_virtio: Introduce caif over virtio

Wed, 20 Mar 2013 03:22:24 +0000

caif_virtio: Introduce caif over virtioAdd the CAIF Virtio shared memory driver for talkingto a modem.This CAIF Link layer communicates to the modem overshared memory. It is implemented as a virtio_driver.The underlying virtio device is managed by the remoteprocframework. The Virtio queue is used for transmitting datato the modem, and the new vringh is used for receiving data.Genalloc is used for managing the shared memory used for TXdata. The default dma-alloc-coherent allocator can onlyallocate whole pages, and this wastes too much shared memory.Flow control is implemented by stopping the TX-queues if thevirtio queues go full or we run out of memory. Queued arereopened when queues are below the watermark.NAPI is used in RX path, and a dedicated tasklet is usedfor releasing TX buffers.Signed-off-by: Erwan Yvin Acked-by: David S. Miller Signed-off-by: Rusty Russell (minor fixes) List of files: /linux-6.15/drivers/net/caif/Makefile

7a875903 - caif: remove caif_shm

Mon, 11 Mar 2013 03:13:03 +0000

caif: remove caif_shmcaif_shm is an old implementationcaif_shm will be replaced by caif_virtio[ As explained by Linus Walleij: "U5500 used this, but was cancelled and the silicon did not reach anyone outside ST-Ericsson. Then for the next platforms, we have gone for the leaner & cleaner approach of using virtio, rpmesg and rproc." ]Signed-off-by: Erwan Yvin Acked-by: Linus Walleij Acked-by: Sjur Brendeland Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/net/caif/Makefile

40d69043 - caif: Add CAIF HSI Link layer driver

Wed, 01 Jun 2011 03:29:18 +0000

caif: Add CAIF HSI Link layer driverThis patch introduces the CAIF HSI Protocol Driver for theCAIF Link Layer.This driver implements a platform driver to accommodate for aplatform specific HSI devices. A general platform driver is notpossible as there are no HSI side Kernel API defined.Signed-off-by: Sjur Brændeland Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/net/caif/Makefile

5a8b7cdc - net: change to new flag variable

Fri, 14 Jan 2011 14:12:45 +0000

net: change to new flag variableReplace EXTRA_CFLAGS with ccflags-y.Signed-off-by: matt mooney Acked-by: WANG Cong Acked-by: Sjur Braendeland Acked-by: David S. Miller Acked-by: John W. Linville Signed-off-by: Michal Marek List of files: /linux-6.15/drivers/net/caif/Makefile

1933f0c0 - caif-u5500: Build config for CAIF shared mem driver

Wed, 27 Oct 2010 08:34:42 +0000

caif-u5500: Build config for CAIF shared mem driverSigned-off-by: Sjur Braendeland Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/net/caif/Makefile

529d6dad - caif-driver: Add CAIF-SPI Protocol driver.

Tue, 29 Jun 2010 07:08:21 +0000

caif-driver: Add CAIF-SPI Protocol driver.This patch introduces the CAIF SPI Protocol Driver forCAIF Link Layer.This driver implements a platform driver to accommodate for aplatform specific SPI device. A general platform driver is notpossible as there are no SPI Slave side Kernel API defined.A sample CAIF SPI Platform device can be found in.../Documentation/networking/caif/spi_porting.txtSigned-off-by: Sjur Braendeland Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/net/caif/Makefile

01eebb53 - caif: Kconfig and Makefile fixes

Sat, 26 Jun 2010 11:31:28 +0000

caif: Kconfig and Makefile fixesUse "depends on" instead of "if" in Kconfig files.Fixed CAIF debug flag, and removed unnecessary clean-* options.Signed-off-by: Sjur Braendeland Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/net/caif/Makefile

9b27105b - net-caif-driver: add CAIF serial driver (ldisc)

Tue, 30 Mar 2010 13:56:30 +0000

net-caif-driver: add CAIF serial driver (ldisc)Add CAIF Serial driver. This driver is implemented as a line discipline.caif_serial uses the following module parameters:ser_use_stx - specifies if STart of frame eXtension is in use.ser_loop - sets the interface in loopback mode.Signed-off-by: Sjur Braendeland Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/net/caif/Makefile