License cleanup: add SPDX GPL-2.0 license identifier to files with no license
Many source files in the tree are missing licensing information, which
makes it harder for compliance tools to determine the correct license.
By default all files without license information are under the default
license 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 binding
shorthand, which can be used instead of the full boiler plate text.
This patch is based on work done by Thomas Gleixner and Kate Stewart and
Philippe Ombredanne.
How this work was done:
Patches were generated and checked against linux-4.14-rc6 for a subset of
the 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 cases
where non-standard license headers were used, and references to license
had to be inferred by heuristics based on keywords.
The analysis to determine which SPDX License Identifier to be applied to
a file was done in a spreadsheet of side by side results from of the
output of two independent scanners (ScanCode & Windriver) producing SPDX
tag:value files created by Philippe Ombredanne. Philippe prepared the
base 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 files
assessed. Kate Stewart did a file by file comparison of the scanner
results in the spreadsheet to determine which SPDX license identifier(s)
to be applied to the file. She confirmed any determination that was not
immediately 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 license
identifiers 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 the
spreadsheet to determine the SPDX license identifiers to apply to the
source files by Kate, Philippe, Thomas and, in some cases, confirmation
by lawyers working with the Linux Foundation.
Kate also obtained a third independent scan of the 4.13 code base from
FOSSology, and compared selected files where the other two scanners
disagreed against that SPDX file, to see if there was new insights. The
Windriver scanner is based on an older version of FOSSology in part, so
they are related.
Thomas did random spot checks in about 500 files from the spreadsheets
for the uapi headers and agreed with SPDX license identifier in the
files he inspected. For the non-uapi files Thomas did random spot checks
in about 15000 files.
In initial set of patches against 4.14-rc6, 3 files were found to have
copy/paste license identifier errors, and have been fixed to reflect the
correct identifier.
Additionally Philippe spent 10 hours this week doing a detailed manual
inspection and review of the 12,461 patched files from the initial patch
version 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 correct
This produced a worksheet with 20 files needing minor correction. This
worksheet was then exported into 3 different .csv files for the
different types of files to be modified.
These .csv files were then reviewed by Greg. Thomas wrote a script to
parse the csv files and add the proper SPDX tag to the file, in the
format that the file expected. This script was further refined by Greg
based on the output to detect more types of files automatically and to
distinguish between header and source .c files (which need different
comment types.) Finally Greg ran the script using the .csv files to
generate the patches.
Reviewed-by: Kate Stewart <kstewart@linuxfoundation.org>
Reviewed-by: Philippe Ombredanne <pombredanne@nexb.com>
Reviewed-by: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2017-11-01 08:07:57 -06:00
|
|
|
# SPDX-License-Identifier: GPL-2.0
|
2008-09-24 15:46:44 -06:00
|
|
|
# Makefile for staging directory
|
|
|
|
|
|
2011-11-01 18:23:55 -06:00
|
|
|
obj-y += media/
|
2008-10-02 12:29:28 -06:00
|
|
|
obj-$(CONFIG_PRISM2_USB) += wlan-ng/
|
2008-11-04 21:29:31 -07:00
|
|
|
obj-$(CONFIG_COMEDI) += comedi/
|
2016-04-04 14:52:35 -06:00
|
|
|
obj-$(CONFIG_FB_OLPC_DCON) += olpc_dcon/
|
2009-11-03 02:17:24 -07:00
|
|
|
obj-$(CONFIG_RTL8192U) += rtl8192u/
|
2009-08-04 16:57:55 -06:00
|
|
|
obj-$(CONFIG_RTL8192E) += rtl8192e/
|
2017-03-29 11:47:51 -06:00
|
|
|
obj-$(CONFIG_RTL8723BS) += rtl8723bs/
|
2010-08-20 09:15:30 -06:00
|
|
|
obj-$(CONFIG_R8712U) += rtl8712/
|
2013-08-21 21:34:15 -06:00
|
|
|
obj-$(CONFIG_R8188EU) += rtl8188eu/
|
2013-11-12 02:16:08 -07:00
|
|
|
obj-$(CONFIG_RTS5208) += rts5208/
|
2013-03-06 07:12:22 -07:00
|
|
|
obj-$(CONFIG_NETLOGIC_XLR_NET) += netlogic/
|
2009-05-05 18:35:21 -06:00
|
|
|
obj-$(CONFIG_OCTEON_ETHERNET) += octeon/
|
2013-06-01 12:42:58 -06:00
|
|
|
obj-$(CONFIG_OCTEON_USB) += octeon-usb/
|
2009-06-02 12:44:46 -06:00
|
|
|
obj-$(CONFIG_VT6655) += vt6655/
|
2009-06-13 05:39:00 -06:00
|
|
|
obj-$(CONFIG_VT6656) += vt6656/
|
2009-09-11 10:51:31 -06:00
|
|
|
obj-$(CONFIG_VME_BUS) += vme/
|
2009-08-18 11:06:19 -06:00
|
|
|
obj-$(CONFIG_IIO) += iio/
|
2015-04-21 21:37:26 -06:00
|
|
|
obj-$(CONFIG_FB_SM750) += sm750fb/
|
2014-06-06 04:44:17 -06:00
|
|
|
obj-$(CONFIG_USB_EMXX) += emxx_udc/
|
2011-02-22 07:27:58 -07:00
|
|
|
obj-$(CONFIG_SPEAKUP) += speakup/
|
2011-05-19 08:34:42 -06:00
|
|
|
obj-$(CONFIG_MFD_NVEC) += nvec/
|
2011-11-30 04:33:10 -07:00
|
|
|
obj-$(CONFIG_ANDROID) += android/
|
2014-06-06 04:44:43 -06:00
|
|
|
obj-$(CONFIG_STAGING_BOARD) += board/
|
2013-07-24 12:36:17 -06:00
|
|
|
obj-$(CONFIG_LTE_GDM724X) += gdm724x/
|
2012-11-02 06:16:33 -06:00
|
|
|
obj-$(CONFIG_FIREWIRE_SERIAL) += fwserial/
|
2013-01-23 07:13:52 -07:00
|
|
|
obj-$(CONFIG_GOLDFISH) += goldfish/
|
2014-01-21 00:47:06 -07:00
|
|
|
obj-$(CONFIG_GS_FPGABOOT) += gs_fpgaboot/
|
2014-03-04 06:58:05 -07:00
|
|
|
obj-$(CONFIG_UNISYSSPAR) += unisys/
|
2014-10-02 10:13:35 -06:00
|
|
|
obj-$(CONFIG_COMMON_CLK_XLNX_CLKWZRD) += clocking-wizard/
|
2014-12-31 02:11:09 -07:00
|
|
|
obj-$(CONFIG_FB_TFT) += fbtft/
|
2017-04-28 03:50:28 -06:00
|
|
|
obj-$(CONFIG_FSL_DPAA2) += fsl-dpaa2/
|
2015-05-10 23:30:56 -06:00
|
|
|
obj-$(CONFIG_WILC1000) += wilc1000/
|
Staging: most: add MOST driver's core module
This patch adds the core module of the MOST driver to the kernel's driver
staging area. This module is part of the MOST driver and handles the
configuration interface in sysfs, the buffer management and the data
routing.
MOST defines the protocol, hardware and software layers necessary to allow
for the efficient and low-cost transport of control, real-time and packet
data using a single medium (physical layer). Media currently in use are
fiber optics, unshielded twisted pair cables (UTP) and coax cables. MOST
also supports various speed grades up to 150 Mbps.
For more information on MOST, visit the MOST Cooperation website:
www.mostcooperation.com.
Cars continue to evolve into sophisticated consumer electronics platforms,
increasing the demand for reliable and simple solutions to support audio,
video and data communications. MOST can be used to connect multiple
consumer devices via optical or electrical physical layers directly to one
another or in a network configuration. As a synchronous network, MOST
provides excellent Quality of Service and seamless connectivity for
audio/video streaming. Therefore, the driver perfectly fits to the mission
of Automotive Grade Linux to create open source software solutions for
automotive applications.
The driver consists basically of three layers. The hardware layer, the
core layer and the application layer. The core layer consists of the core
module only. This module handles the communication flow through all three
layers, the configuration of the driver, the configuration interface
representation in sysfs, and the buffer management.
For each of the other two layers a selection of modules is provided. These
modules can arbitrarily be combined to meet the needs of the desired
system architecture. A module of the hardware layer is referred to as an
HDM (hardware dependent module). Each module of this layer handles exactly
one of the peripheral interfaces of a network interface controller (e.g.
USB, MediaLB, I2C). A module of the application layer is referred to as an
AIM (application interfacing module). The modules of this layer give access
to MOST via one the following ways: character devices, ALSA, Networking or
V4L2.
To physically access MOST, an Intelligent Network Interface Controller
(INIC) is needed. For more information on available controllers visit:
www.microchip.com
Signed-off-by: Christian Gromm <christian.gromm@microchip.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2015-07-24 08:11:48 -06:00
|
|
|
obj-$(CONFIG_MOST) += most/
|
2016-05-31 04:56:13 -06:00
|
|
|
obj-$(CONFIG_KS7010) += ks7010/
|
2016-09-19 07:46:40 -06:00
|
|
|
obj-$(CONFIG_GREYBUS) += greybus/
|
2016-10-26 12:34:21 -06:00
|
|
|
obj-$(CONFIG_BCM2835_VCHIQ) += vc04_services/
|
2017-07-16 04:52:06 -06:00
|
|
|
obj-$(CONFIG_PI433) += pi433/
|
2019-01-15 23:48:43 -07:00
|
|
|
obj-$(CONFIG_PCI_MT7621) += mt7621-pci/
|
|
|
|
|
obj-$(CONFIG_PCI_MT7621_PHY) += mt7621-pci-phy/
|
|
|
|
|
obj-$(CONFIG_PINCTRL_RT2880) += mt7621-pinctrl/
|
2018-03-14 14:22:35 -06:00
|
|
|
obj-$(CONFIG_SOC_MT7621) += mt7621-dma/
|
2019-01-15 23:48:43 -07:00
|
|
|
obj-$(CONFIG_DMA_RALINK) += ralink-gdma/
|
2018-03-14 14:22:36 -06:00
|
|
|
obj-$(CONFIG_SOC_MT7621) += mt7621-dts/
|
drivers/staging: Gasket driver framework + Apex driver
The Gasket (Google ASIC Software, Kernel Extensions, and Tools) kernel
framework is a generic, flexible system that supports thin kernel
drivers. Gasket kernel drivers are expected to handle opening and
closing devices, mmap'ing BAR space as requested, a small selection of
ioctls, and handling page table translation (covered below). Any other
functions should be handled by userspace code.
The Gasket common module is not enough to run a device. In order to
customize the Gasket code for a given piece of hardware, a device
specific module must be created. At a minimum, this module must define a
struct gasket_driver_desc containing the device-specific data for use by
the framework; in addition, the module must declare an __init function
that calls gasket_register_device with the module's gasket_driver_desc
struct. Finally, the driver must define an exit function that calls
gasket_unregister_device with the module's gasket_driver_desc struct.
One of the core assumptions of the Gasket framework is that precisely
one process is allowed to have an open write handle to the device node
at any given time. (That process may, once it has one write handle, open
any number of additional write handles.) This is accomplished by
tracking open and close data for each driver instance.
Signed-off-by: Rob Springer <rspringer@google.com>
Signed-off-by: John Joseph <jnjoseph@google.com>
Signed-off-by: Simon Que <sque@chromium.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2018-06-29 20:49:38 -06:00
|
|
|
obj-$(CONFIG_STAGING_GASKET_FRAMEWORK) += gasket/
|
2018-07-22 19:27:37 -06:00
|
|
|
obj-$(CONFIG_XIL_AXIS_FIFO) += axis-fifo/
|
2018-07-26 06:21:51 -06:00
|
|
|
obj-$(CONFIG_EROFS_FS) += erofs/
|
2019-04-16 09:56:12 -06:00
|
|
|
obj-$(CONFIG_FIELDBUS_DEV) += fieldbus/
|
2019-04-19 12:42:05 -06:00
|
|
|
obj-$(CONFIG_KPC2000) += kpc2000/
|
isdn: move capi drivers to staging
I tried to find any indication of whether the capi drivers are still in
use, and have not found anything from a long time ago.
With public ISDN networks almost completely shut down over the past 12
months, there is very little you can actually do with this hardware. The
main remaining use case would be to connect ISDN voice phones to an
in-house installation with Asterisk or LCR, but anyone trying this in
turn seems to be using either the mISDN driver stack, or out-of-tree
drivers from the hardware vendors.
I may of course have missed something, so I would suggest moving these
three drivers (avm, hysdn, gigaset) into drivers/staging/ just in case
someone still uses them.
If nobody complains, we can remove them entirely in six months, or
otherwise move the core code and any drivers that are still needed back
into drivers/isdn.
As Paul Bolle notes, he is still testing the gigaset driver as long as
he can, but the Dutch ISDN network will be shut down in September 2019,
which puts an end to that.
Marcel Holtmann still maintains the Bluetooth CMTP profile and wants to
keep that alive, so the actual CAPI subsystem code remains in place for
now, after all other drivers are gone, CMTP and CAPI can be merged into
a single driver directory.
Cc: Marcel Holtmann <marcel@holtmann.org>
Cc: Paul Bolle <pebolle@tiscali.nl>
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
2019-04-20 14:28:45 -06:00
|
|
|
obj-$(CONFIG_ISDN_CAPI) += isdn/
|