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 15:07:57 +01:00
# SPDX-License-Identifier: GPL-2.0
2007-10-16 01:29:39 -07:00
menuconfig AGP
2006-06-22 14:47:35 -07:00
tristate "/dev/agpgart (AGP Support)"
2006-08-24 21:33:40 -04:00
depends on ALPHA || IA64 || PARISC || PPC || X86
2006-06-28 13:38:43 -04:00
depends on PCI
2020-06-14 01:50:22 +09:00
help
2005-04-16 15:20:36 -07:00
AGP (Accelerated Graphics Port) is a bus system mainly used to
connect graphics cards to the rest of the system.
If you have an AGP system and you say Y here, it will be possible to
use the AGP features of your 3D rendering video card. This code acts
as a sort of "AGP driver" for the motherboard's chipset.
If you need more texture memory than you can get with the AGP GART
(theoretically up to 256 MB, but in practice usually 64 or 128 MB
due to kernel allocation issues), you could use PCI accesses
and have up to a couple gigs of texture space.
2006-02-10 11:56:30 +01:00
Note that this is the only means to have X/GLX use
2005-04-16 15:20:36 -07:00
write-combining with MTRR support on the AGP bus. Without it, OpenGL
direct rendering will be a lot slower but still faster than PIO.
To compile this driver as a module, choose M here: the
module will be called agpgart.
2006-02-10 11:56:30 +01:00
You should say Y here if you want to use GLX or DRI.
If unsure, say N.
2005-04-16 15:20:36 -07:00
config AGP_ALI
tristate "ALI chipset support"
2005-10-30 14:59:20 -08:00
depends on AGP && X86_32
2020-06-14 01:50:22 +09:00
help
2005-04-16 15:20:36 -07:00
This option gives you AGP support for the GLX component of
2006-02-10 11:56:30 +01:00
X on the following ALi chipsets. The supported chipsets
2005-04-16 15:20:36 -07:00
include M1541, M1621, M1631, M1632, M1641,M1647,and M1651.
For the ALi-chipset question, ALi suggests you refer to
2010-10-18 11:03:14 +02:00
<http://www.ali.com.tw/>.
2005-04-16 15:20:36 -07:00
The M1541 chipset can do AGP 1x and 2x, but note that there is an
acknowledged incompatibility with Matrox G200 cards. Due to
timing issues, this chipset cannot do AGP 2x with the G200.
This is a hardware limitation. AGP 1x seems to be fine, though.
config AGP_ATI
tristate "ATI chipset support"
2005-10-30 14:59:20 -08:00
depends on AGP && X86_32
2020-06-14 01:50:22 +09:00
help
2006-02-10 11:56:30 +01:00
This option gives you AGP support for the GLX component of
X on the ATI RadeonIGP family of chipsets.
2005-04-16 15:20:36 -07:00
config AGP_AMD
tristate "AMD Irongate, 761, and 762 chipset support"
2011-02-01 11:54:15 -05:00
depends on AGP && X86_32
2005-04-16 15:20:36 -07:00
help
This option gives you AGP support for the GLX component of
2006-02-10 11:56:30 +01:00
X on AMD Irongate, 761, and 762 chipsets.
2005-04-16 15:20:36 -07:00
config AGP_AMD64
2009-10-29 17:16:00 +01:00
tristate "AMD Opteron/Athlon64 on-CPU GART support"
2010-09-17 18:03:43 +02:00
depends on AGP && X86 && AMD_NB
2005-04-16 15:20:36 -07:00
help
This option gives you AGP support for the GLX component of
2006-02-10 11:56:30 +01:00
X using the on-CPU northbridge of the AMD Athlon64/Opteron CPUs.
2005-04-16 15:20:36 -07:00
You still need an external AGP bridge like the AMD 8151, VIA
2019-11-20 21:42:47 +08:00
K8T400M, SiS755. It may also support other AGP bridges when loaded
2005-04-16 15:20:36 -07:00
with agp_try_unsupported=1.
config AGP_INTEL
tristate "Intel 440LX/BX/GX, I8xx and E7x05 chipset support"
depends on AGP && X86
2013-11-05 14:00:08 +02:00
select INTEL_GTT
2005-04-16 15:20:36 -07:00
help
2006-02-10 11:56:30 +01:00
This option gives you AGP support for the GLX component of X
2005-04-16 15:20:36 -07:00
on Intel 440LX/BX/GX, 815, 820, 830, 840, 845, 850, 860, 875,
2006-02-10 11:56:30 +01:00
E7205 and E7505 chipsets and full support for the 810, 815, 830M,
845G, 852GM, 855GM, 865G and I915 integrated graphics chipsets.
2005-04-16 15:20:36 -07:00
config AGP_NVIDIA
tristate "NVIDIA nForce/nForce2 chipset support"
2005-10-30 14:59:20 -08:00
depends on AGP && X86_32
2005-04-16 15:20:36 -07:00
help
This option gives you AGP support for the GLX component of
2006-02-10 11:56:30 +01:00
X on NVIDIA chipsets including nForce and nForce2
2005-04-16 15:20:36 -07:00
config AGP_SIS
tristate "SiS chipset support"
2006-12-04 03:43:14 -07:00
depends on AGP && X86
2005-04-16 15:20:36 -07:00
help
This option gives you AGP support for the GLX component of
2006-02-10 11:56:30 +01:00
X on Silicon Integrated Systems [SiS] chipsets.
2005-04-16 15:20:36 -07:00
Note that 5591/5592 AGP chipsets are NOT supported.
config AGP_SWORKS
tristate "Serverworks LE/HE chipset support"
2005-10-30 14:59:20 -08:00
depends on AGP && X86_32
2005-04-16 15:20:36 -07:00
help
2006-02-28 00:54:25 -05:00
Say Y here to support the Serverworks AGP card. See
2005-04-16 15:20:36 -07:00
<http://www.serverworks.com/> for product descriptions and images.
config AGP_VIA
tristate "VIA chipset support"
2006-12-04 03:43:14 -07:00
depends on AGP && X86
2005-04-16 15:20:36 -07:00
help
This option gives you AGP support for the GLX component of
2006-02-10 11:56:30 +01:00
X on VIA MVP3/Apollo Pro chipsets.
2005-04-16 15:20:36 -07:00
config AGP_I460
tristate "Intel 460GX chipset support"
2019-08-13 09:25:12 +02:00
depends on AGP && IA64
2005-04-16 15:20:36 -07:00
help
This option gives you AGP GART support for the Intel 460GX chipset
for IA64 processors.
config AGP_HP_ZX1
tristate "HP ZX1 chipset AGP support"
2019-08-13 09:25:12 +02:00
depends on AGP && IA64
2005-04-16 15:20:36 -07:00
help
This option gives you AGP GART support for the HP ZX1 chipset
for IA64 processors.
2006-08-24 21:33:40 -04:00
config AGP_PARISC
tristate "HP Quicksilver AGP support"
depends on AGP && PARISC && 64BIT
help
This option gives you AGP GART support for the HP Quicksilver
AGP bus adapter on HP PA-RISC machines (Ok, just on the C8000
workstation...)
2005-04-16 15:20:36 -07:00
config AGP_ALPHA_CORE
tristate "Alpha AGP support"
depends on AGP && (ALPHA_GENERIC || ALPHA_TITAN || ALPHA_MARVEL)
default AGP
config AGP_UNINORTH
tristate "Apple UniNorth & U3 AGP support"
depends on AGP && PPC_PMAC
help
This option gives you AGP support for Apple machines with a
UniNorth or U3 (Apple G5) bridge.
config AGP_EFFICEON
tristate "Transmeta Efficeon support"
2005-10-30 14:59:20 -08:00
depends on AGP && X86_32
2005-04-16 15:20:36 -07:00
help
This option gives you AGP support for the Transmeta Efficeon
series processors with integrated northbridges.
2013-11-05 14:00:08 +02:00
config INTEL_GTT
tristate
depends on X86 && PCI