Changes in 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/rapidio/Makefile

b6e8d4aa - rapidio: add RapidIO channelized messaging driver

Tue, 02 Aug 2016 21:06:25 +0000

rapidio: add RapidIO channelized messaging driverAdd channelized messaging driver to support native RapidIO messagingexchange between multiple senders/recipients on devices that use kernelRapidIO subsystem services.This device driver is the result of collaboration within the RapidIO.orgSoftware Task Group (STG) between Texas Instruments, ProdriveTechnologies, Nokia Networks, BAE and IDT. Additional input wasreceived from other members of RapidIO.org.The objective was to create a character mode driver interface whichexposes messaging capabilities of RapidIO endpoint devices (mports)directly to applications, in a manner that allows the numerous andvaried RapidIO implementations to interoperate.This char mode device driver allows user-space applications to setupmessaging communication channels using single shared RapidIO messagingmailbox.By default this driver uses RapidIO MBOX_1 (MBOX_0 is reserved for use byRIONET Ethernet emulation driver).[weiyj.lk@gmail.com: rapidio/rio_cm: fix return value check in riocm_init()] Link: http://lkml.kernel.org/r/1469198221-21970-1-git-send-email-alexandre.bounine@idt.comLink: http://lkml.kernel.org/r/1468952862-18056-1-git-send-email-alexandre.bounine@idt.comSigned-off-by: Alexandre Bounine Tested-by: Barry Wood Cc: Matt Porter Cc: Aurelien Jacquiot Cc: Andre van Herk Cc: Barry Wood Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds List of files: /linux-6.15/drivers/rapidio/Makefile

fdf90abc - rapidio: add modular build option for the subsystem core

Wed, 03 Jul 2013 22:08:56 +0000

rapidio: add modular build option for the subsystem coreAdd a configuration option to build RapidIO subsystem core code as aloadable kernel module. Currently this option is available only forx86-based platforms, with the additional patch for PowerPC planned to beprovided later.This patch replaces kernel command line parameter "riohdid=" with itsmodule-specific analog "rapidio.hdid=".Signed-off-by: Alexandre Bounine Cc: Matt Porter Cc: Li Yang Cc: Kumar Gala Cc: Andre van Herk Cc: Micha Nelissen Cc: Stef van Os Cc: Jean Delvare Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds List of files: /linux-6.15/drivers/rapidio/Makefile

a11650e1 - rapidio: make enumeration/discovery configurable

Fri, 24 May 2013 22:55:05 +0000

rapidio: make enumeration/discovery configurableSystems that use RapidIO fabric may need to implement their ownenumeration and discovery methods which are better suitable for needs ofa target application.The following set of patches is intended to simplify process ofintroduction of new RapidIO fabric enumeration/discovery methods.The first patch offers ability to add new RapidIO enumeration/discoverymethods using kernel configuration options. This new configurationoption mechanism allows to select statically linked or modularenumeration/discovery method(s) from the list of existing methods or useexternal module(s).This patch also updates the currently existing enumeration/discoverycode to be used as a statically linked or modular method.The corresponding configuration option is named "Basicenumeration/discovery" method. This is the only one configurationoption available today but new methods are expected to be introducedafter adoption of provided patches.The second patch address a long time complaint of RapidIO subsystemusers regarding fabric enumeration/discovery start sequence. Existingimplementation offers only a boot-time enumeration/discovery start whichrequires synchronized boot of all endpoints in RapidIO network. Whileit works for small closed configurations with limited number ofendpoints, using this approach in systems with large number of endpointsis quite challenging.To eliminate requirement for synchronized start the second patchintroduces RapidIO enumeration/discovery start from user space.For compatibility with the existing RapidIO subsystem implementation,automatic boot time enumeration/discovery start can be configured in byspecifying "rio-scan.scan=1" command line parameter if statically linkedbasic enumeration method is selected.This patch:Rework to implement RapidIO enumeration/discovery method selectioncombined with ability to use enumeration/discovery as a kernel module.This patch adds ability to introduce new RapidIO enumeration/discoverymethods using kernel configuration options. Configuration optionmechanism allows to select statically linked or modularenumeration/discovery method from the list of existing methods or useexternal modules. If a modular enumeration/discovery is selected eachRapidIO mport device can have its own method attached to it.The existing enumeration/discovery code was updated to be used asstatically linked or modular method. This configuration option is named"Basic enumeration/discovery" method.Several common routines have been moved from rio-scan.c to make themavailable to other enumeration methods and reduce number of exportedsymbols.Signed-off-by: Alexandre Bounine Cc: Matt Porter Cc: Li Yang Cc: Kumar Gala Cc: Andre van Herk Cc: Micha Nelissen Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds List of files: /linux-6.15/drivers/rapidio/Makefile

48618fb4 - RapidIO: add mport driver for Tsi721 bridge

Wed, 02 Nov 2011 20:39:09 +0000

RapidIO: add mport driver for Tsi721 bridgeAdd RapidIO mport driver for IDT TSI721 PCI Express-to-SRIO bridge device. The driver provides full set of callback functions defined for mportdevices in RapidIO subsystem. It also is compatible with current versionof RIONET driver (Ethernet over RapidIO messaging services).This patch is applicable to kernel versions starting from 2.6.39.Signed-off-by: Alexandre Bounine Signed-off-by: Chul Kim Cc: Kumar Gala Cc: Matt Porter Cc: Li Yang Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds List of files: /linux-6.15/drivers/rapidio/Makefile

4ebdd58f - rapidio: change to new flag variable

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

rapidio: change to new flag variableswitches/ depends on RAPIDIO_DEBUG so the subdir-ccflags-y variantseems to be appropriate here.Signed-off-by: matt mooney Acked-by: WANG Cong Signed-off-by: Michal Marek List of files: /linux-6.15/drivers/rapidio/Makefile

011507e4 - rapidio: add debug configuration option

Wed, 26 May 2010 21:44:03 +0000

rapidio: add debug configuration optionAdd debug configuration option for RapidIO subsystem.Signed-off-by: Alexandre Bounine Cc: Matt Porter Cc: Li Yang Cc: Kumar Gala Cc: Thomas Moll Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds List of files: /linux-6.15/drivers/rapidio/Makefile

394b701c - [PATCH] RapidIO support: core base

Mon, 07 Nov 2005 09:00:15 +0000

[PATCH] RapidIO support: core baseAdds a RapidIO subsystem to the kernel. RIO is a switched fabric interconnectused in higher-end embedded applications. The curious can look at the specsover at http://www.rapidio.orgThe core code implements enumeration/discovery, management ofdevices/resources, and interfaces for RIO drivers.There's a lot more to do to take advantages of all the hardware features.However, this should provide a good base for folks with RIO hardware to startcontributing.Signed-off-by: Matt Porter Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds List of files: /linux-6.15/drivers/rapidio/Makefile