forked from luck/tmp_suning_uos_patched
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>
122 lines
4.4 KiB
C
122 lines
4.4 KiB
C
/* SPDX-License-Identifier: GPL-2.0 */
|
|
/*
|
|
-------------------------------------------------------------------------------
|
|
The macro `BITS64' can be defined to indicate that 64-bit integer types are
|
|
supported by the compiler.
|
|
-------------------------------------------------------------------------------
|
|
*/
|
|
#define BITS64
|
|
|
|
/*
|
|
-------------------------------------------------------------------------------
|
|
Each of the following `typedef's defines the most convenient type that holds
|
|
integers of at least as many bits as specified. For example, `uint8' should
|
|
be the most convenient type that can hold unsigned integers of as many as
|
|
8 bits. The `flag' type must be able to hold either a 0 or 1. For most
|
|
implementations of C, `flag', `uint8', and `int8' should all be `typedef'ed
|
|
to the same as `int'.
|
|
-------------------------------------------------------------------------------
|
|
*/
|
|
typedef char flag;
|
|
typedef unsigned char uint8;
|
|
typedef signed char int8;
|
|
typedef int uint16;
|
|
typedef int int16;
|
|
typedef unsigned int uint32;
|
|
typedef signed int int32;
|
|
#ifdef BITS64
|
|
typedef unsigned long long int bits64;
|
|
typedef signed long long int sbits64;
|
|
#endif
|
|
|
|
/*
|
|
-------------------------------------------------------------------------------
|
|
Each of the following `typedef's defines a type that holds integers
|
|
of _exactly_ the number of bits specified. For instance, for most
|
|
implementation of C, `bits16' and `sbits16' should be `typedef'ed to
|
|
`unsigned short int' and `signed short int' (or `short int'), respectively.
|
|
-------------------------------------------------------------------------------
|
|
*/
|
|
typedef unsigned char bits8;
|
|
typedef signed char sbits8;
|
|
typedef unsigned short int bits16;
|
|
typedef signed short int sbits16;
|
|
typedef unsigned int bits32;
|
|
typedef signed int sbits32;
|
|
#ifdef BITS64
|
|
typedef unsigned long long int uint64;
|
|
typedef signed long long int int64;
|
|
#endif
|
|
|
|
#ifdef BITS64
|
|
/*
|
|
-------------------------------------------------------------------------------
|
|
The `LIT64' macro takes as its argument a textual integer literal and if
|
|
necessary ``marks'' the literal as having a 64-bit integer type. For
|
|
example, the Gnu C Compiler (`gcc') requires that 64-bit literals be
|
|
appended with the letters `LL' standing for `long long', which is `gcc's
|
|
name for the 64-bit integer type. Some compilers may allow `LIT64' to be
|
|
defined as the identity macro: `#define LIT64( a ) a'.
|
|
-------------------------------------------------------------------------------
|
|
*/
|
|
#define LIT64( a ) a##LL
|
|
#endif
|
|
|
|
/*
|
|
-------------------------------------------------------------------------------
|
|
The macro `INLINE' can be used before functions that should be inlined. If
|
|
a compiler does not support explicit inlining, this macro should be defined
|
|
to be `static'.
|
|
-------------------------------------------------------------------------------
|
|
*/
|
|
#define INLINE static inline
|
|
|
|
|
|
/* For use as a GCC soft-float library we need some special function names. */
|
|
|
|
#ifdef __LIBFLOAT__
|
|
|
|
/* Some 32-bit ops can be mapped straight across by just changing the name. */
|
|
#define float32_add __addsf3
|
|
#define float32_sub __subsf3
|
|
#define float32_mul __mulsf3
|
|
#define float32_div __divsf3
|
|
#define int32_to_float32 __floatsisf
|
|
#define float32_to_int32_round_to_zero __fixsfsi
|
|
#define float32_to_uint32_round_to_zero __fixunssfsi
|
|
|
|
/* These ones go through the glue code. To avoid namespace pollution
|
|
we rename the internal functions too. */
|
|
#define float32_eq ___float32_eq
|
|
#define float32_le ___float32_le
|
|
#define float32_lt ___float32_lt
|
|
|
|
/* All the 64-bit ops have to go through the glue, so we pull the same
|
|
trick. */
|
|
#define float64_add ___float64_add
|
|
#define float64_sub ___float64_sub
|
|
#define float64_mul ___float64_mul
|
|
#define float64_div ___float64_div
|
|
#define int32_to_float64 ___int32_to_float64
|
|
#define float64_to_int32_round_to_zero ___float64_to_int32_round_to_zero
|
|
#define float64_to_uint32_round_to_zero ___float64_to_uint32_round_to_zero
|
|
#define float64_to_float32 ___float64_to_float32
|
|
#define float32_to_float64 ___float32_to_float64
|
|
#define float64_eq ___float64_eq
|
|
#define float64_le ___float64_le
|
|
#define float64_lt ___float64_lt
|
|
|
|
#if 0
|
|
#define float64_add __adddf3
|
|
#define float64_sub __subdf3
|
|
#define float64_mul __muldf3
|
|
#define float64_div __divdf3
|
|
#define int32_to_float64 __floatsidf
|
|
#define float64_to_int32_round_to_zero __fixdfsi
|
|
#define float64_to_uint32_round_to_zero __fixunsdfsi
|
|
#define float64_to_float32 __truncdfsf2
|
|
#define float32_to_float64 __extendsfdf2
|
|
#endif
|
|
|
|
#endif
|