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 21:07:57 +07:00
|
|
|
# SPDX-License-Identifier: GPL-2.0
|
2009-11-24 02:40:01 +07:00
|
|
|
# au1000-style gpio and interrupt controllers
|
|
|
|
|
config ALCHEMY_GPIOINT_AU1000
|
MIPS: Alchemy: Rewrite GPIO support.
The current in-kernel Alchemy GPIO support is far too inflexible for
all my use cases. To address this, the following changes are made:
* create generic functions which deal with manipulating the on-chip
GPIO1/2 blocks. Such functions are universally useful.
* Macros for GPIO2 shared interrupt management and block control.
* support for both built-in CONFIG_GPIOLIB and fast, inlined GPIO macros.
If CONFIG_GPIOLIB is not enabled, provide linux gpio framework
compatibility by directly inlining the GPIO1/2 functions. GPIO access
is limited to on-chip ones and they can be accessed as documented in
the datasheets (GPIO0-31 and 200-215).
If CONFIG_GPIOLIB is selected, two (2) gpio_chip-s, one for GPIO1 and
one for GPIO2, are registered. GPIOs can still be accessed by using
the numberspace established in the databooks.
However this is not yet flexible enough for my uses: My Alchemy
systems have a documented "external" gpio interface (fixed, different
numberspace) and can support a variety of baseboards, some of which
are equipped with I2C gpio expanders. I want to be able to provide
the default 16 GPIOs of the CPU board numbered as 0..15 and also
support gpio expanders, if present, starting as gpio16.
To achieve this, a new Kconfig symbol for Alchemy is introduced,
CONFIG_ALCHEMY_GPIO_INDIRECT, which boards can enable to signal
that they don't want the Alchemy numberspace exposed to the outside
world, but instead want to provide their own. Boards are now respon-
sible for providing the linux gpio interface glue code (either in a
custom gpio.h header (in board include directory) or with gpio_chips).
To make the board-specific inlined gpio functions work, the MIPS
Makefile must be changed so that the mach-au1x00/gpio.h header is
included _after_ the board headers, by moving the inclusion of
the mach-au1x00/ to the end of the header list.
See arch/mips/include/asm/mach-au1x00/gpio.h for more info.
Signed-off-by: Manuel Lauss <manuel.lauss@gmail.com>
Acked-by: Florian Fainelli <florian@openwrt.org>
Signed-off-by: Ralf Baechle <ralf@linux-mips.org>
2009-06-06 19:09:55 +07:00
|
|
|
bool
|
|
|
|
|
|
2011-11-02 02:03:30 +07:00
|
|
|
# au1300-style GPIO/INT controller
|
|
|
|
|
config ALCHEMY_GPIOINT_AU1300
|
|
|
|
|
bool
|
|
|
|
|
|
2007-05-11 18:44:30 +07:00
|
|
|
choice
|
|
|
|
|
prompt "Machine type"
|
2010-07-16 02:45:04 +07:00
|
|
|
depends on MIPS_ALCHEMY
|
2014-02-20 20:59:24 +07:00
|
|
|
default MIPS_DB1XXX
|
2007-05-11 18:44:30 +07:00
|
|
|
|
|
|
|
|
config MIPS_MTX1
|
|
|
|
|
bool "4G Systems MTX-1 board"
|
2018-11-16 02:05:32 +07:00
|
|
|
select HAVE_PCI
|
2011-08-12 16:39:45 +07:00
|
|
|
select ALCHEMY_GPIOINT_AU1000
|
2007-05-11 18:44:30 +07:00
|
|
|
select SYS_SUPPORTS_LITTLE_ENDIAN
|
2009-10-15 23:49:27 +07:00
|
|
|
select SYS_HAS_EARLY_PRINTK
|
2007-05-11 18:44:30 +07:00
|
|
|
|
2014-02-20 20:59:24 +07:00
|
|
|
config MIPS_DB1XXX
|
|
|
|
|
bool "Alchemy DB1XXX / PB1XXX boards"
|
2016-04-19 16:23:22 +07:00
|
|
|
select GPIOLIB
|
2018-11-16 02:05:32 +07:00
|
|
|
select HAVE_PCI
|
2007-05-11 18:44:30 +07:00
|
|
|
select SYS_SUPPORTS_LITTLE_ENDIAN
|
2009-10-15 23:49:27 +07:00
|
|
|
select SYS_HAS_EARLY_PRINTK
|
2014-02-20 20:59:24 +07:00
|
|
|
help
|
|
|
|
|
Select this option if you have one of the following Alchemy
|
|
|
|
|
development boards: DB1000 DB1500 DB1100 DB1550 DB1200 DB1300
|
|
|
|
|
PB1500 PB1100 PB1550 PB1200
|
|
|
|
|
Board type is autodetected during boot.
|
2007-05-11 18:44:30 +07:00
|
|
|
|
|
|
|
|
config MIPS_XXS1500
|
|
|
|
|
bool "MyCable XXS1500 board"
|
2011-08-12 16:39:45 +07:00
|
|
|
select ALCHEMY_GPIOINT_AU1000
|
2007-05-11 18:44:30 +07:00
|
|
|
select SYS_SUPPORTS_LITTLE_ENDIAN
|
2009-10-15 23:49:27 +07:00
|
|
|
select SYS_HAS_EARLY_PRINTK
|
2007-05-11 18:44:30 +07:00
|
|
|
|
2010-07-15 16:21:23 +07:00
|
|
|
config MIPS_GPR
|
|
|
|
|
bool "Trapeze ITS GPR board"
|
2011-08-12 16:39:45 +07:00
|
|
|
select ALCHEMY_GPIOINT_AU1000
|
2018-11-16 02:05:32 +07:00
|
|
|
select HAVE_PCI
|
2010-07-15 16:21:23 +07:00
|
|
|
select SYS_SUPPORTS_LITTLE_ENDIAN
|
|
|
|
|
select SYS_HAS_EARLY_PRINTK
|
|
|
|
|
|
2007-05-11 18:44:30 +07:00
|
|
|
endchoice
|