mirror of
https://github.com/edk2-porting/linux-next.git
synced 2024-12-22 20:23:57 +08:00
b24413180f
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>
146 lines
4.4 KiB
Plaintext
146 lines
4.4 KiB
Plaintext
# SPDX-License-Identifier: GPL-2.0
|
|
if MMU
|
|
|
|
config ARCH_MAY_HAVE_PC_FDC
|
|
bool
|
|
depends on BROKEN && (Q40 || SUN3X)
|
|
default y
|
|
|
|
menu "Platform devices"
|
|
|
|
config HEARTBEAT
|
|
bool "Use power LED as a heartbeat" if AMIGA || APOLLO || ATARI || Q40
|
|
default y if !AMIGA && !APOLLO && !ATARI && !Q40 && HP300
|
|
help
|
|
Use the power-on LED on your machine as a load meter. The exact
|
|
behavior is platform-dependent, but normally the flash frequency is
|
|
a hyperbolic function of the 5-minute load average.
|
|
|
|
# We have a dedicated heartbeat LED. :-)
|
|
config PROC_HARDWARE
|
|
bool "/proc/hardware support"
|
|
help
|
|
Say Y here to support the /proc/hardware file, which gives you
|
|
access to information about the machine you're running on,
|
|
including the model, CPU, MMU, clock speed, BogoMIPS rating,
|
|
and memory size.
|
|
|
|
config NATFEAT
|
|
bool "ARAnyM emulator support"
|
|
depends on ATARI
|
|
help
|
|
This option enables support for ARAnyM native features, such as
|
|
access to a disk image as /dev/hda.
|
|
|
|
config NFBLOCK
|
|
tristate "NatFeat block device support"
|
|
depends on BLOCK && NATFEAT
|
|
help
|
|
Say Y to include support for the ARAnyM NatFeat block device
|
|
which allows direct access to the hard drives without using
|
|
the hardware emulation.
|
|
|
|
config NFCON
|
|
tristate "NatFeat console driver"
|
|
depends on TTY && NATFEAT
|
|
help
|
|
Say Y to include support for the ARAnyM NatFeat console driver
|
|
which allows the console output to be redirected to the stderr
|
|
output of ARAnyM.
|
|
|
|
config NFETH
|
|
tristate "NatFeat Ethernet support"
|
|
depends on ETHERNET && NATFEAT
|
|
help
|
|
Say Y to include support for the ARAnyM NatFeat network device
|
|
which will emulate a regular ethernet device while presenting an
|
|
ethertap device to the host system.
|
|
|
|
config ATARI_ETHERNAT
|
|
bool "Atari EtherNAT Ethernet support"
|
|
depends on ATARI
|
|
---help---
|
|
Say Y to include support for the EtherNAT network adapter for the
|
|
CT/60 extension port.
|
|
|
|
To compile the actual ethernet driver, choose Y or M for the SMC91X
|
|
option in the network device section; the module will be called smc91x.
|
|
|
|
config ATARI_ETHERNEC
|
|
bool "Atari EtherNEC Ethernet support"
|
|
depends on ATARI_ROM_ISA
|
|
---help---
|
|
Say Y to include support for the EtherNEC network adapter for the
|
|
ROM port. The driver works by polling instead of interrupts, so it
|
|
is quite slow.
|
|
|
|
This driver also supports the ethernet part of the NetUSBee ROM
|
|
port combined Ethernet/USB adapter.
|
|
|
|
To compile the actual ethernet driver, choose Y or M in for the NE2000
|
|
option in the network device section; the module will be called ne.
|
|
|
|
endmenu
|
|
|
|
menu "Character devices"
|
|
|
|
config ATARI_DSP56K
|
|
tristate "Atari DSP56k support"
|
|
depends on ATARI
|
|
help
|
|
If you want to be able to use the DSP56001 in Falcons, say Y. This
|
|
driver is still experimental, and if you don't know what it is, or
|
|
if you don't have this processor, just say N.
|
|
|
|
To compile this driver as a module, choose M here.
|
|
|
|
config AMIGA_BUILTIN_SERIAL
|
|
tristate "Amiga builtin serial support"
|
|
depends on AMIGA && TTY
|
|
help
|
|
If you want to use your Amiga's built-in serial port in Linux,
|
|
answer Y.
|
|
|
|
To compile this driver as a module, choose M here.
|
|
|
|
config HPDCA
|
|
tristate "HP DCA serial support"
|
|
depends on DIO && SERIAL_8250
|
|
help
|
|
If you want to use the internal "DCA" serial ports on an HP300
|
|
machine, say Y here.
|
|
|
|
config HPAPCI
|
|
tristate "HP APCI serial support"
|
|
depends on HP300 && SERIAL_8250
|
|
help
|
|
If you want to use the internal "APCI" serial ports on an HP400
|
|
machine, say Y here.
|
|
|
|
config SERIAL_CONSOLE
|
|
bool "Support for serial port console"
|
|
depends on AMIGA_BUILTIN_SERIAL=y
|
|
---help---
|
|
If you say Y here, it will be possible to use a serial port as the
|
|
system console (the system console is the device which receives all
|
|
kernel messages and warnings and which allows logins in single user
|
|
mode). This could be useful if some terminal or printer is connected
|
|
to that serial port.
|
|
|
|
Even if you say Y here, the currently visible virtual console
|
|
(/dev/tty0) will still be used as the system console by default, but
|
|
you can alter that using a kernel command line option such as
|
|
"console=ttyS1". (Try "man bootparam" or see the documentation of
|
|
your boot loader about how to pass options to the kernel at boot
|
|
time.)
|
|
|
|
If you don't have a graphical console and you say Y here, the
|
|
kernel will automatically use the first serial line, /dev/ttyS0, as
|
|
system console.
|
|
|
|
If unsure, say N.
|
|
|
|
endmenu
|
|
|
|
endif
|