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/bcma/Makefile

d6a3b51a - bcma: move parallel flash support to separated file

Fri, 12 Feb 2016 09:15:44 +0000

bcma: move parallel flash support to separated fileThis follows the way of handling other flashes and cleans code a bit. Asnext task we will want to move flash code to ChipCommon driver as:1) Flash controllers are accesible using ChipCommon registers2) This code isn't MIPS specificThis change prepares bcma for that.Signed-off-by: Rafał Miłecki Signed-off-by: Kalle Valo List of files: /linux-6.15/drivers/bcma/Makefile

1ca2760f - bcma: prepare Kconfig symbol for PCI driver

Wed, 04 Mar 2015 22:07:05 +0000

bcma: prepare Kconfig symbol for PCI driverDriver for PCIe core requires PCI to be enabled, however we shouldn'trequire it for the whole bus. Someone may be not interested in extraPCI devices and what's more there are SoCs without any PCI at all (likeBCM5356C0, BCM5357*, BCM47186B0). For more details see Kconfig "help".Please note this patch doesn't allow disabling PCI drivers yet, as itrequires more work on calls to bcma_core_pci_* functions.Signed-off-by: Rafał Miłecki Signed-off-by: Kalle Valo List of files: /linux-6.15/drivers/bcma/Makefile

1716bcf3 - bcma: add support for chipcommon B core

Mon, 08 Sep 2014 20:53:36 +0000

bcma: add support for chipcommon B coreThis core is used on BCM4708 to configure the PCIe and USB3 PHYs and itcontains the addresses to the Device Management unit. This will be usedby the PCIe driver first.Signed-off-by: Hauke Mehrtens Signed-off-by: John W. Linville List of files: /linux-6.15/drivers/bcma/Makefile

f473832f - bcma: add driver for PCIe Gen 2 core

Fri, 04 Jul 2014 23:10:41 +0000

bcma: add driver for PCIe Gen 2 coreNew Broadcom PCIe devices (802.11ac ones?) use Gen2 and have to beinitialized differently.Signed-off-by: Rafał Miłecki Signed-off-by: John W. Linville List of files: /linux-6.15/drivers/bcma/Makefile

cf0936b0 - bcma: add GPIO driver

Tue, 20 Nov 2012 22:24:30 +0000

bcma: add GPIO driverRegister a GPIO driver to access the GPIOs provided by the chip.The GPIOs of the SoC should always start at 0 and the other GPIOs couldstart at a random position. There is just one SoC in a system and whenthey start at 0 the number is predictable.Signed-off-by: Hauke Mehrtens Patchwork: http://patchwork.linux-mips.org/patch/4587Acked-by: Florian Fainelli List of files: /linux-6.15/drivers/bcma/Makefile

23cb3b21 - bcma: add place for flash memory support

Tue, 17 Jul 2012 14:26:41 +0000

bcma: add place for flash memory supportSigned-off-by: Rafał Miłecki Signed-off-by: John W. Linville List of files: /linux-6.15/drivers/bcma/Makefile

e1ac4b40 - bcma: add trivial GBIT MAC COMMON driver

Wed, 11 Jul 2012 07:23:43 +0000

bcma: add trivial GBIT MAC COMMON driverGMAC COMMON core is present on BCM4706 and is used for example to accessboard PHYs (PHYs can not be accessed directly using GBIT MAC core).Signed-off-by: Rafał Miłecki Acked-by: Hauke Mehrtens Signed-off-by: John W. Linville List of files: /linux-6.15/drivers/bcma/Makefile

21e0534a - bcma: add mips driver

Fri, 22 Jul 2011 23:20:09 +0000

bcma: add mips driverThis adds a mips driver to bcma. This is only found on embeddeddevices. For now the driver just initializes the irqs used on thissystem.Signed-off-by: Hauke Mehrtens Acked-by: Ralf Baechle Signed-off-by: John W. Linville List of files: /linux-6.15/drivers/bcma/Makefile

ecd177c2 - bcma: add SOC bus

Fri, 22 Jul 2011 23:20:08 +0000

bcma: add SOC busThis patch adds support for using bcma on a Broadcom SoC as the systembus. An SoC like the bcm4716 could register this bus and use it tosearches for the bcma cores and register the devices on this bus.BCMA_HOSTTYPE_NONE was intended for SoCs at first but BCMA_HOSTTYPE_SOCis a better name.Acked-by: Rafał Miłecki Signed-off-by: Hauke Mehrtens Acked-by: Ralf Baechle Signed-off-by: John W. Linville List of files: /linux-6.15/drivers/bcma/Makefile

9352f69c - bcma: detect PCI core working in hostmode

Tue, 05 Jul 2011 17:48:26 +0000

bcma: detect PCI core working in hostmodeWe must not init it like clientmode one, it would break device (testedby Hauke on BCM4718). Add stub hostmode driver for now.Signed-off-by: Rafał Miłecki Signed-off-by: Hauke Mehrtens Signed-off-by: John W. Linville List of files: /linux-6.15/drivers/bcma/Makefile

27f18dc2 - bcma: read SPROM and extract MAC from it

Thu, 02 Jun 2011 00:08:51 +0000

bcma: read SPROM and extract MAC from itIn case of BCMA cards SPROM is located in the ChipCommon core, it isnot mapped as separated host window. So far we have met only SPROMs rev8.SPROM layout seems to be the same as for SSB buses, so we decided toshare SPROM struct and some defines.For now we extract MAC address only, this can be improved of course.Signed-off-by: Rafał Miłecki Signed-off-by: John W. Linville List of files: /linux-6.15/drivers/bcma/Makefile

8369ae33 - bcma: add Broadcom specific AMBA bus driver

Mon, 09 May 2011 16:56:46 +0000

bcma: add Broadcom specific AMBA bus driverBroadcom has released cards based on a new AMBA-based bus type. From aprogramming point of view, this new bus type differs from AMBA and doesnot use AMBA common registers. It also differs enough from SSB. Wedecided that a new bus driver is needed to keep the code clean.In its current form, the driver detects devices present on the bus andregisters them in the system. It allows registering BCMA drivers forspecified bus devices and provides them basic operations. The bus driveritself includes two important bus managing drivers: ChipCommon coredriver and PCI(c) core driver. They are early used to allow correctinitialization.Currently code is limited to supporting buses on PCI(e) devices, howeverthe driver is designed to be used also on other hosts. The hostabstraction layer is implemented and already used for PCI(e).Support for PCI(e) hosts is working and seems to be stable (access to80211 core was tested successfully on a few devices). We can stilloptimize it by using some fixed windows, but this can be done laterwithout affecting any external code. Windows are just ranges in MMIOused for accessing cores on the bus.Cc: Greg KH Cc: Michael Büsch Cc: Larry Finger Cc: George Kashperko Cc: Arend van Spriel Cc: linux-arm-kernel@lists.infradead.orgCc: Russell King Cc: Arnd Bergmann Cc: Andy Botting Cc: linuxdriverproject Cc: linux-kernel@vger.kernel.org Signed-off-by: Rafał Miłecki Signed-off-by: John W. Linville List of files: /linux-6.15/drivers/bcma/Makefile