summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/export-to-postgresql.py
diff options
context:
space:
mode:
authorJonathan Corbet <corbet@lwn.net>2018-04-27 16:48:42 -0600
committerJonathan Corbet <corbet@lwn.net>2018-04-27 16:48:42 -0600
commitd6331e0b14e6f2371b89e6b36137e1c2ed756c0c (patch)
tree66ee4ad7e475ec5406d9f81ad5498619809d15d6 /tools/perf/scripts/python/export-to-postgresql.py
parente37274fa3a2b9b96926b471bf681554ac56d5749 (diff)
parent5385a295ec00eb80525ec7ff1d97e13e06ba77b7 (diff)
Merge branch 'tglx-license' into docs-next
Thomas said: There are a few bogus SPDX identifiers in various files and SPDX Identifiers used in tree or about to be used which have no corresponding License Text file in the LICENSES directory or use the new variant of the GPL-2.0[+] license identifiers which are not mentioned in the GPL-2.0 Valid-License-Identifiers: tags. There is no tool which can be used to scan the tree and also nothing which helps people who submit patches to check their stuff before submission. The following series cleans that up: - Add GPL-2.0-only and GPL-2.0-or-later identifiers to the GPL2.0 license and the Linux-syscall-note exception - Add X11, Apache-2.0, CC-BY-SA-4.0, CCDL-1.0, Linux-OpenIB license texts to the LICENSES directory along with the required documentation texts - Add a checker script which can read a single file or even a patch from the command line or does a full git tree scan [Thomas also wins some sort of special prize for including an SPDX-checking patch that complains about itself!]
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions