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 22:07:57 +08:00
|
|
|
# SPDX-License-Identifier: GPL-2.0
|
2011-10-04 22:54:51 +08:00
|
|
|
#
|
|
|
|
# For a description of the syntax of this configuration file,
|
2019-06-13 01:52:48 +08:00
|
|
|
# see Documentation/kbuild/kconfig-language.rst.
|
2011-10-04 22:54:51 +08:00
|
|
|
#
|
|
|
|
|
2012-05-02 08:37:49 +08:00
|
|
|
config C6X
|
2011-10-04 22:54:51 +08:00
|
|
|
def_bool y
|
32-bit userspace ABI: introduce ARCH_32BIT_OFF_T config option
All new 32-bit architectures should have 64-bit userspace off_t type, but
existing architectures has 32-bit ones.
To enforce the rule, new config option is added to arch/Kconfig that defaults
ARCH_32BIT_OFF_T to be disabled for new 32-bit architectures. All existing
32-bit architectures enable it explicitly.
New option affects force_o_largefile() behaviour. Namely, if userspace
off_t is 64-bits long, we have no reason to reject user to open big files.
Note that even if architectures has only 64-bit off_t in the kernel
(arc, c6x, h8300, hexagon, nios2, openrisc, and unicore32),
a libc may use 32-bit off_t, and therefore want to limit the file size
to 4GB unless specified differently in the open flags.
Signed-off-by: Yury Norov <ynorov@caviumnetworks.com>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Yury Norov <ynorov@marvell.com>
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
2018-05-16 16:18:49 +08:00
|
|
|
select ARCH_32BIT_OFF_T
|
2019-06-13 15:08:57 +08:00
|
|
|
select ARCH_HAS_BINFMT_FLAT
|
2018-04-16 23:27:40 +08:00
|
|
|
select ARCH_HAS_SYNC_DMA_FOR_CPU
|
|
|
|
select ARCH_HAS_SYNC_DMA_FOR_DEVICE
|
2011-10-04 22:54:51 +08:00
|
|
|
select CLKDEV_LOOKUP
|
2020-04-09 14:44:13 +08:00
|
|
|
select HAVE_LEGACY_CLK
|
2012-08-16 00:12:16 +08:00
|
|
|
select GENERIC_ATOMIC64
|
2011-10-04 22:54:51 +08:00
|
|
|
select GENERIC_IRQ_SHOW
|
|
|
|
select HAVE_ARCH_TRACEHOOK
|
2012-01-26 10:02:40 +08:00
|
|
|
select SPARSE_IRQ
|
2012-01-26 22:26:21 +08:00
|
|
|
select IRQ_DOMAIN
|
2011-10-04 22:54:51 +08:00
|
|
|
select OF
|
|
|
|
select OF_EARLY_FLATTREE
|
2012-05-19 00:45:46 +08:00
|
|
|
select GENERIC_CLOCKEVENTS
|
2012-09-28 13:01:03 +08:00
|
|
|
select MODULES_USE_ELF_RELA
|
2018-09-04 23:04:07 +08:00
|
|
|
select MMU_GATHER_NO_RANGE if MMU
|
2011-10-04 22:54:51 +08:00
|
|
|
|
|
|
|
config MMU
|
|
|
|
def_bool n
|
|
|
|
|
|
|
|
config FPU
|
|
|
|
def_bool n
|
|
|
|
|
|
|
|
config GENERIC_CALIBRATE_DELAY
|
|
|
|
def_bool y
|
|
|
|
|
|
|
|
config GENERIC_HWEIGHT
|
|
|
|
def_bool y
|
|
|
|
|
|
|
|
config GENERIC_BUG
|
|
|
|
def_bool y
|
2016-03-18 05:21:06 +08:00
|
|
|
depends on BUG
|
2011-10-04 22:54:51 +08:00
|
|
|
|
|
|
|
config C6X_BIG_KERNEL
|
|
|
|
bool "Build a big kernel"
|
|
|
|
help
|
|
|
|
The C6X function call instruction has a limited range of +/- 2MiB.
|
|
|
|
This is sufficient for most kernels, but some kernel configurations
|
|
|
|
with lots of compiled-in functionality may require a larger range
|
|
|
|
for function calls. Use this option to have the compiler generate
|
|
|
|
function calls with 32-bit range. This will make the kernel both
|
|
|
|
larger and slower.
|
|
|
|
|
|
|
|
If unsure, say N.
|
|
|
|
|
|
|
|
# Use the generic interrupt handling code in kernel/irq/
|
|
|
|
|
|
|
|
config CMDLINE_BOOL
|
|
|
|
bool "Default bootloader kernel arguments"
|
|
|
|
|
|
|
|
config CMDLINE
|
|
|
|
string "Kernel command line"
|
|
|
|
depends on CMDLINE_BOOL
|
|
|
|
default "console=ttyS0,57600"
|
|
|
|
help
|
|
|
|
On some architectures there is currently no way for the boot loader
|
|
|
|
to pass arguments to the kernel. For these architectures, you should
|
|
|
|
supply some command-line options at build time by entering them
|
|
|
|
here.
|
|
|
|
|
|
|
|
config CMDLINE_FORCE
|
|
|
|
bool "Force default kernel command string"
|
|
|
|
depends on CMDLINE_BOOL
|
|
|
|
default n
|
|
|
|
help
|
|
|
|
Set this to have arguments from the default kernel command string
|
|
|
|
override those passed by the boot loader.
|
|
|
|
|
|
|
|
config CPU_BIG_ENDIAN
|
|
|
|
bool "Build big-endian kernel"
|
|
|
|
default n
|
|
|
|
help
|
|
|
|
Say Y if you plan on running a kernel in big-endian mode.
|
|
|
|
Note that your board must be properly built and your board
|
|
|
|
port must properly enable any big-endian related features
|
|
|
|
of your chipset/board/processor.
|
|
|
|
|
|
|
|
config FORCE_MAX_ZONEORDER
|
|
|
|
int "Maximum zone order"
|
|
|
|
default "13"
|
|
|
|
help
|
|
|
|
The kernel memory allocator divides physically contiguous memory
|
|
|
|
blocks into "zones", where each zone is a power of two number of
|
|
|
|
pages. This option selects the largest power of two that the kernel
|
|
|
|
keeps in the memory allocator. If you need to allocate very large
|
|
|
|
blocks of physically contiguous memory, then you may need to
|
|
|
|
increase this value.
|
|
|
|
|
|
|
|
This config option is actually maximum order plus one. For example,
|
|
|
|
a value of 11 means that the largest free memory block is 2^10 pages.
|
|
|
|
|
|
|
|
menu "Processor type and features"
|
|
|
|
|
|
|
|
source "arch/c6x/platforms/Kconfig"
|
|
|
|
|
|
|
|
config KERNEL_RAM_BASE_ADDRESS
|
|
|
|
hex "Virtual address of memory base"
|
|
|
|
default 0xe0000000 if SOC_TMS320C6455
|
|
|
|
default 0xe0000000 if SOC_TMS320C6457
|
|
|
|
default 0xe0000000 if SOC_TMS320C6472
|
|
|
|
default 0x80000000
|
|
|
|
|
|
|
|
source "kernel/Kconfig.hz"
|
|
|
|
|
|
|
|
endmenu
|