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 17:07:57 +03:00
|
|
|
# SPDX-License-Identifier: GPL-2.0
|
2005-04-17 02:20:36 +04:00
|
|
|
#
|
|
|
|
|
# PARIDE configuration
|
|
|
|
|
#
|
|
|
|
|
# PARIDE doesn't need PARPORT, but if PARPORT is configured as a module,
|
2007-02-10 12:46:28 +03:00
|
|
|
# PARIDE must also be a module.
|
2006-01-06 11:19:49 +03:00
|
|
|
# PARIDE only supports PC style parports. Tough for USB or other parports...
|
2005-04-17 02:20:36 +04:00
|
|
|
|
|
|
|
|
comment "Parallel IDE high-level drivers"
|
|
|
|
|
depends on PARIDE
|
|
|
|
|
|
|
|
|
|
config PARIDE_PD
|
|
|
|
|
tristate "Parallel port IDE disks"
|
|
|
|
|
depends on PARIDE
|
|
|
|
|
help
|
|
|
|
|
This option enables the high-level driver for IDE-type disk devices
|
|
|
|
|
connected through a parallel port. If you chose to build PARIDE
|
|
|
|
|
support into your kernel, you may answer Y here to build in the
|
|
|
|
|
parallel port IDE driver, otherwise you should answer M to build
|
|
|
|
|
it as a loadable module. The module will be called pd. You
|
|
|
|
|
must also have at least one parallel port protocol driver in your
|
|
|
|
|
system. Among the devices supported by this driver are the SyQuest
|
|
|
|
|
EZ-135, EZ-230 and SparQ drives, the Avatar Shark and the backpack
|
|
|
|
|
hard drives from MicroSolutions.
|
|
|
|
|
|
|
|
|
|
config PARIDE_PCD
|
|
|
|
|
tristate "Parallel port ATAPI CD-ROMs"
|
|
|
|
|
depends on PARIDE
|
2017-10-30 19:02:19 +03:00
|
|
|
select CDROM
|
2017-01-28 11:32:51 +03:00
|
|
|
select BLK_SCSI_REQUEST # only for the generic cdrom code
|
2020-06-13 19:50:22 +03:00
|
|
|
help
|
2005-04-17 02:20:36 +04:00
|
|
|
This option enables the high-level driver for ATAPI CD-ROM devices
|
|
|
|
|
connected through a parallel port. If you chose to build PARIDE
|
|
|
|
|
support into your kernel, you may answer Y here to build in the
|
|
|
|
|
parallel port ATAPI CD-ROM driver, otherwise you should answer M to
|
|
|
|
|
build it as a loadable module. The module will be called pcd. You
|
|
|
|
|
must also have at least one parallel port protocol driver in your
|
|
|
|
|
system. Among the devices supported by this driver are the
|
|
|
|
|
MicroSolutions backpack CD-ROM drives and the Freecom Power CD. If
|
|
|
|
|
you have such a CD-ROM drive, you should also say Y or M to "ISO
|
|
|
|
|
9660 CD-ROM file system support" below, because that's the file
|
|
|
|
|
system used on CD-ROMs.
|
|
|
|
|
|
|
|
|
|
config PARIDE_PF
|
|
|
|
|
tristate "Parallel port ATAPI disks"
|
|
|
|
|
depends on PARIDE
|
|
|
|
|
help
|
|
|
|
|
This option enables the high-level driver for ATAPI disk devices
|
|
|
|
|
connected through a parallel port. If you chose to build PARIDE
|
|
|
|
|
support into your kernel, you may answer Y here to build in the
|
|
|
|
|
parallel port ATAPI disk driver, otherwise you should answer M
|
|
|
|
|
to build it as a loadable module. The module will be called pf.
|
|
|
|
|
You must also have at least one parallel port protocol driver in
|
|
|
|
|
your system. Among the devices supported by this driver are the
|
|
|
|
|
MicroSolutions backpack PD/CD drive and the Imation Superdisk
|
|
|
|
|
LS-120 drive.
|
|
|
|
|
|
|
|
|
|
config PARIDE_PT
|
|
|
|
|
tristate "Parallel port ATAPI tapes"
|
|
|
|
|
depends on PARIDE
|
|
|
|
|
help
|
|
|
|
|
This option enables the high-level driver for ATAPI tape devices
|
|
|
|
|
connected through a parallel port. If you chose to build PARIDE
|
|
|
|
|
support into your kernel, you may answer Y here to build in the
|
|
|
|
|
parallel port ATAPI disk driver, otherwise you should answer M
|
|
|
|
|
to build it as a loadable module. The module will be called pt.
|
|
|
|
|
You must also have at least one parallel port protocol driver in
|
|
|
|
|
your system. Among the devices supported by this driver is the
|
|
|
|
|
parallel port version of the HP 5GB drive.
|
|
|
|
|
|
|
|
|
|
config PARIDE_PG
|
|
|
|
|
tristate "Parallel port generic ATAPI devices"
|
|
|
|
|
depends on PARIDE
|
2020-06-13 19:50:22 +03:00
|
|
|
help
|
2005-04-17 02:20:36 +04:00
|
|
|
This option enables a special high-level driver for generic ATAPI
|
|
|
|
|
devices connected through a parallel port. The driver allows user
|
|
|
|
|
programs, such as cdrtools, to send ATAPI commands directly to a
|
|
|
|
|
device.
|
|
|
|
|
|
|
|
|
|
If you chose to build PARIDE support into your kernel, you may
|
|
|
|
|
answer Y here to build in the parallel port generic ATAPI driver,
|
|
|
|
|
otherwise you should answer M to build it as a loadable module. The
|
|
|
|
|
module will be called pg.
|
|
|
|
|
|
|
|
|
|
You must also have at least one parallel port protocol driver in
|
|
|
|
|
your system.
|
|
|
|
|
|
|
|
|
|
This driver implements an API loosely related to the generic SCSI
|
|
|
|
|
driver. See <file:include/linux/pg.h>. for details.
|
|
|
|
|
|
|
|
|
|
You can obtain the most recent version of cdrtools from
|
|
|
|
|
<ftp://ftp.berlios.de/pub/cdrecord/>. Versions 1.6.1a3 and
|
|
|
|
|
later fully support this driver.
|
|
|
|
|
|
|
|
|
|
comment "Parallel IDE protocol modules"
|
|
|
|
|
depends on PARIDE
|
|
|
|
|
|
|
|
|
|
config PARIDE_ATEN
|
|
|
|
|
tristate "ATEN EH-100 protocol"
|
|
|
|
|
depends on PARIDE
|
|
|
|
|
help
|
|
|
|
|
This option enables support for the ATEN EH-100 parallel port IDE
|
|
|
|
|
protocol. This protocol is used in some inexpensive low performance
|
|
|
|
|
parallel port kits made in Hong Kong. If you chose to build PARIDE
|
|
|
|
|
support into your kernel, you may answer Y here to build in the
|
|
|
|
|
protocol driver, otherwise you should answer M to build it as a
|
|
|
|
|
loadable module. The module will be called aten. You must also
|
|
|
|
|
have a high-level driver for the type of device that you want to
|
|
|
|
|
support.
|
|
|
|
|
|
|
|
|
|
config PARIDE_BPCK
|
|
|
|
|
tristate "MicroSolutions backpack (Series 5) protocol"
|
|
|
|
|
depends on PARIDE
|
2020-06-13 19:50:22 +03:00
|
|
|
help
|
2005-04-17 02:20:36 +04:00
|
|
|
This option enables support for the Micro Solutions BACKPACK
|
|
|
|
|
parallel port Series 5 IDE protocol. (Most BACKPACK drives made
|
|
|
|
|
before 1999 were Series 5) Series 5 drives will NOT always have the
|
|
|
|
|
Series noted on the bottom of the drive. Series 6 drivers will.
|
|
|
|
|
|
|
|
|
|
In other words, if your BACKPACK drive doesn't say "Series 6" on the
|
|
|
|
|
bottom, enable this option.
|
|
|
|
|
|
|
|
|
|
If you chose to build PARIDE support into your kernel, you may
|
|
|
|
|
answer Y here to build in the protocol driver, otherwise you should
|
|
|
|
|
answer M to build it as a loadable module. The module will be
|
|
|
|
|
called bpck. You must also have a high-level driver for the type
|
|
|
|
|
of device that you want to support.
|
|
|
|
|
|
|
|
|
|
config PARIDE_BPCK6
|
|
|
|
|
tristate "MicroSolutions backpack (Series 6) protocol"
|
|
|
|
|
depends on PARIDE && !64BIT
|
2020-06-13 19:50:22 +03:00
|
|
|
help
|
2005-04-17 02:20:36 +04:00
|
|
|
This option enables support for the Micro Solutions BACKPACK
|
|
|
|
|
parallel port Series 6 IDE protocol. (Most BACKPACK drives made
|
|
|
|
|
after 1999 were Series 6) Series 6 drives will have the Series noted
|
|
|
|
|
on the bottom of the drive. Series 5 drivers don't always have it
|
|
|
|
|
noted.
|
|
|
|
|
|
|
|
|
|
In other words, if your BACKPACK drive says "Series 6" on the
|
|
|
|
|
bottom, enable this option.
|
|
|
|
|
|
|
|
|
|
If you chose to build PARIDE support into your kernel, you may
|
|
|
|
|
answer Y here to build in the protocol driver, otherwise you should
|
|
|
|
|
answer M to build it as a loadable module. The module will be
|
|
|
|
|
called bpck6. You must also have a high-level driver for the type
|
|
|
|
|
of device that you want to support.
|
|
|
|
|
|
|
|
|
|
config PARIDE_COMM
|
|
|
|
|
tristate "DataStor Commuter protocol"
|
|
|
|
|
depends on PARIDE
|
|
|
|
|
help
|
|
|
|
|
This option enables support for the Commuter parallel port IDE
|
|
|
|
|
protocol from DataStor. If you chose to build PARIDE support
|
|
|
|
|
into your kernel, you may answer Y here to build in the protocol
|
|
|
|
|
driver, otherwise you should answer M to build it as a loadable
|
|
|
|
|
module. The module will be called comm. You must also have
|
|
|
|
|
a high-level driver for the type of device that you want to support.
|
|
|
|
|
|
|
|
|
|
config PARIDE_DSTR
|
|
|
|
|
tristate "DataStor EP-2000 protocol"
|
|
|
|
|
depends on PARIDE
|
|
|
|
|
help
|
|
|
|
|
This option enables support for the EP-2000 parallel port IDE
|
|
|
|
|
protocol from DataStor. If you chose to build PARIDE support
|
|
|
|
|
into your kernel, you may answer Y here to build in the protocol
|
|
|
|
|
driver, otherwise you should answer M to build it as a loadable
|
|
|
|
|
module. The module will be called dstr. You must also have
|
|
|
|
|
a high-level driver for the type of device that you want to support.
|
|
|
|
|
|
|
|
|
|
config PARIDE_FIT2
|
|
|
|
|
tristate "FIT TD-2000 protocol"
|
|
|
|
|
depends on PARIDE
|
|
|
|
|
help
|
|
|
|
|
This option enables support for the TD-2000 parallel port IDE
|
|
|
|
|
protocol from Fidelity International Technology. This is a simple
|
|
|
|
|
(low speed) adapter that is used in some portable hard drives. If
|
|
|
|
|
you chose to build PARIDE support into your kernel, you may answer Y
|
|
|
|
|
here to build in the protocol driver, otherwise you should answer M
|
|
|
|
|
to build it as a loadable module. The module will be called ktti.
|
|
|
|
|
You must also have a high-level driver for the type of device that
|
|
|
|
|
you want to support.
|
|
|
|
|
|
|
|
|
|
config PARIDE_FIT3
|
|
|
|
|
tristate "FIT TD-3000 protocol"
|
|
|
|
|
depends on PARIDE
|
|
|
|
|
help
|
|
|
|
|
This option enables support for the TD-3000 parallel port IDE
|
|
|
|
|
protocol from Fidelity International Technology. This protocol is
|
|
|
|
|
used in newer models of their portable disk, CD-ROM and PD/CD
|
|
|
|
|
devices. If you chose to build PARIDE support into your kernel, you
|
|
|
|
|
may answer Y here to build in the protocol driver, otherwise you
|
|
|
|
|
should answer M to build it as a loadable module. The module will be
|
|
|
|
|
called fit3. You must also have a high-level driver for the type
|
|
|
|
|
of device that you want to support.
|
|
|
|
|
|
|
|
|
|
config PARIDE_EPAT
|
|
|
|
|
tristate "Shuttle EPAT/EPEZ protocol"
|
|
|
|
|
depends on PARIDE
|
|
|
|
|
help
|
|
|
|
|
This option enables support for the EPAT parallel port IDE protocol.
|
|
|
|
|
EPAT is a parallel port IDE adapter manufactured by Shuttle
|
|
|
|
|
Technology and widely used in devices from major vendors such as
|
|
|
|
|
Hewlett-Packard, SyQuest, Imation and Avatar. If you chose to build
|
|
|
|
|
PARIDE support into your kernel, you may answer Y here to build in
|
|
|
|
|
the protocol driver, otherwise you should answer M to build it as a
|
|
|
|
|
loadable module. The module will be called epat. You must also
|
|
|
|
|
have a high-level driver for the type of device that you want to
|
|
|
|
|
support.
|
|
|
|
|
|
|
|
|
|
config PARIDE_EPATC8
|
2013-01-17 06:53:30 +04:00
|
|
|
bool "Support c7/c8 chips"
|
|
|
|
|
depends on PARIDE_EPAT
|
2005-04-17 02:20:36 +04:00
|
|
|
help
|
|
|
|
|
This option enables support for the newer Shuttle EP1284 (aka c7 and
|
|
|
|
|
c8) chip. You need this if you are using any recent Imation SuperDisk
|
|
|
|
|
(LS-120) drive.
|
|
|
|
|
|
|
|
|
|
config PARIDE_EPIA
|
|
|
|
|
tristate "Shuttle EPIA protocol"
|
|
|
|
|
depends on PARIDE
|
|
|
|
|
help
|
|
|
|
|
This option enables support for the (obsolete) EPIA parallel port
|
|
|
|
|
IDE protocol from Shuttle Technology. This adapter can still be
|
|
|
|
|
found in some no-name kits. If you chose to build PARIDE support
|
|
|
|
|
into your kernel, you may answer Y here to build in the protocol
|
|
|
|
|
driver, otherwise you should answer M to build it as a loadable
|
|
|
|
|
module. The module will be called epia. You must also have a
|
|
|
|
|
high-level driver for the type of device that you want to support.
|
|
|
|
|
|
|
|
|
|
config PARIDE_FRIQ
|
|
|
|
|
tristate "Freecom IQ ASIC-2 protocol"
|
|
|
|
|
depends on PARIDE
|
|
|
|
|
help
|
|
|
|
|
This option enables support for version 2 of the Freecom IQ parallel
|
|
|
|
|
port IDE adapter. This adapter is used by the Maxell Superdisk
|
|
|
|
|
drive. If you chose to build PARIDE support into your kernel, you
|
|
|
|
|
may answer Y here to build in the protocol driver, otherwise you
|
|
|
|
|
should answer M to build it as a loadable module. The module will be
|
|
|
|
|
called friq. You must also have a high-level driver for the type
|
|
|
|
|
of device that you want to support.
|
|
|
|
|
|
|
|
|
|
config PARIDE_FRPW
|
|
|
|
|
tristate "FreeCom power protocol"
|
|
|
|
|
depends on PARIDE
|
|
|
|
|
help
|
|
|
|
|
This option enables support for the Freecom power parallel port IDE
|
|
|
|
|
protocol. If you chose to build PARIDE support into your kernel, you
|
|
|
|
|
may answer Y here to build in the protocol driver, otherwise you
|
|
|
|
|
should answer M to build it as a loadable module. The module will be
|
|
|
|
|
called frpw. You must also have a high-level driver for the type
|
|
|
|
|
of device that you want to support.
|
|
|
|
|
|
|
|
|
|
config PARIDE_KBIC
|
|
|
|
|
tristate "KingByte KBIC-951A/971A protocols"
|
|
|
|
|
depends on PARIDE
|
|
|
|
|
help
|
|
|
|
|
This option enables support for the KBIC-951A and KBIC-971A parallel
|
|
|
|
|
port IDE protocols from KingByte Information Corp. KingByte's
|
|
|
|
|
adapters appear in many no-name portable disk and CD-ROM products,
|
|
|
|
|
especially in Europe. If you chose to build PARIDE support into your
|
|
|
|
|
kernel, you may answer Y here to build in the protocol driver,
|
|
|
|
|
otherwise you should answer M to build it as a loadable module. The
|
|
|
|
|
module will be called kbic. You must also have a high-level driver
|
|
|
|
|
for the type of device that you want to support.
|
|
|
|
|
|
|
|
|
|
config PARIDE_KTTI
|
|
|
|
|
tristate "KT PHd protocol"
|
|
|
|
|
depends on PARIDE
|
|
|
|
|
help
|
|
|
|
|
This option enables support for the "PHd" parallel port IDE protocol
|
|
|
|
|
from KT Technology. This is a simple (low speed) adapter that is
|
|
|
|
|
used in some 2.5" portable hard drives. If you chose to build PARIDE
|
|
|
|
|
support into your kernel, you may answer Y here to build in the
|
|
|
|
|
protocol driver, otherwise you should answer M to build it as a
|
|
|
|
|
loadable module. The module will be called ktti. You must also
|
|
|
|
|
have a high-level driver for the type of device that you want to
|
|
|
|
|
support.
|
|
|
|
|
|
|
|
|
|
config PARIDE_ON20
|
|
|
|
|
tristate "OnSpec 90c20 protocol"
|
|
|
|
|
depends on PARIDE
|
|
|
|
|
help
|
|
|
|
|
This option enables support for the (obsolete) 90c20 parallel port
|
|
|
|
|
IDE protocol from OnSpec (often marketed under the ValuStore brand
|
|
|
|
|
name). If you chose to build PARIDE support into your kernel, you
|
|
|
|
|
may answer Y here to build in the protocol driver, otherwise you
|
|
|
|
|
should answer M to build it as a loadable module. The module will
|
|
|
|
|
be called on20. You must also have a high-level driver for the
|
|
|
|
|
type of device that you want to support.
|
|
|
|
|
|
|
|
|
|
config PARIDE_ON26
|
|
|
|
|
tristate "OnSpec 90c26 protocol"
|
|
|
|
|
depends on PARIDE
|
|
|
|
|
help
|
|
|
|
|
This option enables support for the 90c26 parallel port IDE protocol
|
|
|
|
|
from OnSpec Electronics (often marketed under the ValuStore brand
|
|
|
|
|
name). If you chose to build PARIDE support into your kernel, you
|
|
|
|
|
may answer Y here to build in the protocol driver, otherwise you
|
|
|
|
|
should answer M to build it as a loadable module. The module will be
|
|
|
|
|
called on26. You must also have a high-level driver for the type
|
|
|
|
|
of device that you want to support.
|
|
|
|
|
|
|
|
|
|
#
|
