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 */
|
2005-04-17 05:20:36 +07:00
|
|
|
/*
|
|
|
|
nubus.h: various definitions and prototypes for NuBus drivers to use.
|
|
|
|
|
|
|
|
Originally written by Alan Cox.
|
|
|
|
|
|
|
|
Hacked to death by C. Scott Ananian and David Huggins-Daines.
|
|
|
|
|
|
|
|
Some of the constants in here are from the corresponding
|
|
|
|
NetBSD/OpenBSD header file, by Allen Briggs. We figured out the
|
|
|
|
rest of them on our own. */
|
|
|
|
#ifndef LINUX_NUBUS_H
|
|
|
|
#define LINUX_NUBUS_H
|
|
|
|
|
|
|
|
#include <asm/nubus.h>
|
2012-10-13 16:46:48 +07:00
|
|
|
#include <uapi/linux/nubus.h>
|
2005-04-17 05:20:36 +07:00
|
|
|
|
|
|
|
struct nubus_board {
|
|
|
|
struct nubus_board* next;
|
|
|
|
struct nubus_dev* first_dev;
|
|
|
|
|
2007-05-02 03:32:53 +07:00
|
|
|
/* Only 9-E actually exist, though 0-8 are also theoretically
|
2005-04-17 05:20:36 +07:00
|
|
|
possible, and 0 is a special case which represents the
|
|
|
|
motherboard and onboard peripherals (Ethernet, video) */
|
|
|
|
int slot;
|
|
|
|
/* For slot 0, this is bogus. */
|
|
|
|
char name[64];
|
|
|
|
|
|
|
|
/* Format block */
|
|
|
|
unsigned char* fblock;
|
|
|
|
/* Root directory (does *not* always equal fblock + doffset!) */
|
|
|
|
unsigned char* directory;
|
|
|
|
|
|
|
|
unsigned long slot_addr;
|
|
|
|
/* Offset to root directory (sometimes) */
|
|
|
|
unsigned long doffset;
|
|
|
|
/* Length over which to compute the crc */
|
|
|
|
unsigned long rom_length;
|
|
|
|
/* Completely useless most of the time */
|
|
|
|
unsigned long crc;
|
|
|
|
unsigned char rev;
|
|
|
|
unsigned char format;
|
|
|
|
unsigned char lanes;
|
|
|
|
};
|
|
|
|
|
|
|
|
struct nubus_dev {
|
|
|
|
/* Next link in device list */
|
|
|
|
struct nubus_dev* next;
|
|
|
|
/* Directory entry in /proc/bus/nubus */
|
|
|
|
struct proc_dir_entry* procdir;
|
|
|
|
|
|
|
|
/* The functional resource ID of this device */
|
|
|
|
unsigned char resid;
|
|
|
|
/* These are mostly here for convenience; we could always read
|
|
|
|
them from the ROMs if we wanted to */
|
|
|
|
unsigned short category;
|
|
|
|
unsigned short type;
|
|
|
|
unsigned short dr_sw;
|
|
|
|
unsigned short dr_hw;
|
|
|
|
/* This is the device's name rather than the board's.
|
|
|
|
Sometimes they are different. Usually the board name is
|
|
|
|
more correct. */
|
|
|
|
char name[64];
|
|
|
|
/* MacOS driver (I kid you not) */
|
|
|
|
unsigned char* driver;
|
|
|
|
/* Actually this is an offset */
|
|
|
|
unsigned long iobase;
|
|
|
|
unsigned long iosize;
|
|
|
|
unsigned char flags, hwdevid;
|
|
|
|
|
|
|
|
/* Functional directory */
|
|
|
|
unsigned char* directory;
|
|
|
|
/* Much of our info comes from here */
|
|
|
|
struct nubus_board* board;
|
|
|
|
};
|
|
|
|
|
|
|
|
/* This is all NuBus devices (used to find devices later on) */
|
|
|
|
extern struct nubus_dev* nubus_devices;
|
|
|
|
/* This is all NuBus cards */
|
|
|
|
extern struct nubus_board* nubus_boards;
|
|
|
|
|
|
|
|
/* Generic NuBus interface functions, modelled after the PCI interface */
|
|
|
|
void nubus_scan_bus(void);
|
2013-04-10 21:05:38 +07:00
|
|
|
#ifdef CONFIG_PROC_FS
|
2005-04-17 05:20:36 +07:00
|
|
|
extern void nubus_proc_init(void);
|
2013-04-10 21:05:38 +07:00
|
|
|
#else
|
|
|
|
static inline void nubus_proc_init(void) {}
|
|
|
|
#endif
|
2005-04-17 05:20:36 +07:00
|
|
|
int get_nubus_list(char *buf);
|
|
|
|
int nubus_proc_attach_device(struct nubus_dev *dev);
|
|
|
|
/* If we need more precision we can add some more of these */
|
|
|
|
struct nubus_dev* nubus_find_device(unsigned short category,
|
|
|
|
unsigned short type,
|
|
|
|
unsigned short dr_hw,
|
|
|
|
unsigned short dr_sw,
|
|
|
|
const struct nubus_dev* from);
|
|
|
|
struct nubus_dev* nubus_find_type(unsigned short category,
|
|
|
|
unsigned short type,
|
|
|
|
const struct nubus_dev* from);
|
|
|
|
/* Might have more than one device in a slot, you know... */
|
|
|
|
struct nubus_dev* nubus_find_slot(unsigned int slot,
|
|
|
|
const struct nubus_dev* from);
|
|
|
|
|
|
|
|
/* These are somewhat more NuBus-specific. They all return 0 for
|
|
|
|
success and -1 for failure, as you'd expect. */
|
|
|
|
|
|
|
|
/* The root directory which contains the board and functional
|
|
|
|
directories */
|
|
|
|
int nubus_get_root_dir(const struct nubus_board* board,
|
|
|
|
struct nubus_dir* dir);
|
|
|
|
/* The board directory */
|
|
|
|
int nubus_get_board_dir(const struct nubus_board* board,
|
|
|
|
struct nubus_dir* dir);
|
|
|
|
/* The functional directory */
|
|
|
|
int nubus_get_func_dir(const struct nubus_dev* dev,
|
|
|
|
struct nubus_dir* dir);
|
|
|
|
|
|
|
|
/* These work on any directory gotten via the above */
|
|
|
|
int nubus_readdir(struct nubus_dir* dir,
|
|
|
|
struct nubus_dirent* ent);
|
|
|
|
int nubus_find_rsrc(struct nubus_dir* dir,
|
|
|
|
unsigned char rsrc_type,
|
|
|
|
struct nubus_dirent* ent);
|
|
|
|
int nubus_rewinddir(struct nubus_dir* dir);
|
|
|
|
|
|
|
|
/* Things to do with directory entries */
|
|
|
|
int nubus_get_subdir(const struct nubus_dirent* ent,
|
|
|
|
struct nubus_dir* dir);
|
|
|
|
void nubus_get_rsrc_mem(void* dest,
|
|
|
|
const struct nubus_dirent *dirent,
|
|
|
|
int len);
|
|
|
|
void nubus_get_rsrc_str(void* dest,
|
|
|
|
const struct nubus_dirent *dirent,
|
|
|
|
int maxlen);
|
|
|
|
#endif /* LINUX_NUBUS_H */
|