From: Thomas Gleixner <tglx@linutronix.de>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Kate Stewart <kstewart@linuxfoundation.org>,
Jonathan Corbet <corbet@lwn.net>
Subject: [patch 0/9] treewide: Cleanup recently added license mess
Date: Fri, 18 Jan 2019 00:14:16 +0100 [thread overview]
Message-ID: <20190117231416.111952141@linutronix.de> (raw)
Recently added files or recently added SPDX license identifiers introcuded
license conflicts due to contradicting SPDX license identifiers and boiler
plate text or sloppy license notices.
That's really sad. Quite some people have put a lot of effort into cleaning
up the licensing mess and provided detailed documentation.
It's about time that everyone in the community understands that licensing
is not just an annoyance. It's a really important part of the project and
has legal implication even on the personal level.
The following series addresses recently added crimes. The patches are in a
series but are indenpendent of each other so they are intended to be
applied by the relevant maintainers after thorough review.
Unfortunately we don't have a consistency scanner at the moment. That's a
non trivial problem as the license mess throughout the kernel is horrible
in general. I'm working on a scanner bot which will at least catch newly
added SPDX related inconsistencies. But that will take a while.
Thanks,
tglx
8<------------
block/blk-mq-debugfs-zoned.c | 2 --
crypto/aegis.h | 7 +------
crypto/aegis128.c | 6 +-----
crypto/aegis128l.c | 6 +-----
crypto/aegis256.c | 6 +-----
crypto/morus1280.c | 6 +-----
crypto/morus640.c | 6 +-----
drivers/vfio/pci/trace.h | 6 +-----
drivers/vfio/pci/vfio_pci_nvlink2.c | 6 +-----
fs/ceph/quota.c | 13 -------------
fs/cifs/trace.c | 10 ----------
fs/cifs/trace.h | 10 ----------
include/crypto/morus1280_glue.h | 7 +------
include/crypto/morus640_glue.h | 7 +------
include/crypto/morus_common.h | 7 +------
tools/bpf/bpftool/json_writer.c | 7 +------
tools/bpf/bpftool/json_writer.h | 7 +------
17 files changed, 13 insertions(+), 106 deletions(-)
next reply other threads:[~2019-01-17 23:15 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-17 23:14 Thomas Gleixner [this message]
2019-01-17 23:14 ` [patch 1/9] block: Cleanup license notice Thomas Gleixner
2019-01-18 2:53 ` Bart Van Assche
2019-01-18 4:21 ` Jens Axboe
2019-01-17 23:14 ` [patch 2/9] crypto: aegis - Cleanup license mess Thomas Gleixner
2019-01-18 8:02 ` Ondrej Mosnáček
2019-01-25 10:47 ` Herbert Xu
2019-01-17 23:14 ` [patch 3/9] crypto: morus " Thomas Gleixner
2019-01-18 0:26 ` Fabio Estevam
2019-01-18 6:50 ` Greg Kroah-Hartman
2019-01-18 8:00 ` Ondrej Mosnáček
2019-01-17 23:14 ` [patch 4/9] crypto: aegis - Convert to SPDX license identifiers Thomas Gleixner
2019-01-18 8:01 ` Ondrej Mosnáček
2019-01-17 23:14 ` [patch 5/9] crypto: morus " Thomas Gleixner
2019-01-18 8:02 ` Ondrej Mosnáček
2019-01-17 23:14 ` [patch 6/9] ceph: quota: Cleanup license mess Thomas Gleixner
2019-01-18 9:42 ` Luis Henriques
2019-01-18 10:48 ` Ilya Dryomov
2019-01-18 10:54 ` Thomas Gleixner
2019-01-17 23:14 ` [patch 7/9] smb3: " Thomas Gleixner
2019-01-19 5:43 ` Steve French
2019-01-17 23:14 ` [patch 8/9] tools: bpftool: " Thomas Gleixner
2019-01-17 23:24 ` Jakub Kicinski
2019-01-18 0:00 ` Thomas Gleixner
2019-01-18 23:28 ` Alexei Starovoitov
2019-01-17 23:14 ` [patch 9/9] vfio/pci: " Thomas Gleixner
2019-01-23 20:05 ` Alex Williamson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190117231416.111952141@linutronix.de \
--to=tglx@linutronix.de \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=kstewart@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome