From: "Zavras, Alexios" <alexios.zavras@intel.com>
To: Greg KH <gregkh@linuxfoundation.org>,
"linux-spdx@vger.kernel.org" <linux-spdx@vger.kernel.org>
Subject: libtraceevent license
Date: Mon, 7 Oct 2019 17:46:58 +0000 [thread overview]
Message-ID: <DM5PR1101MB23626F3C7EA8EBA17B2F64DA899B0@DM5PR1101MB2362.namprd11.prod.outlook.com> (raw)
Hi Greg and fellow SPDX curators 😉
One of our developers came to me with a question/complaint:
-----
I'm trying to use libtraceevent -- a library for parsing Linux ring buffer format.
Source code is located in the Linux kernel repository at https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/tools/lib/traceevent
The thing confusing me is that almost all of the files are licensed LGPL-2.1
but the Makefiles and some .c files (some of the plugins of this library),
are licensed GPL-2.0.
-----
Checking the sources, I find three C files:
tools/lib/traceevent/plugins/plugin_cfg80211.c
tools/lib/traceevent/plugins/plugin_scsi.c
tools/lib/traceevent/plugins/plugin_xen.c
I see that the "GPL-2.0" SPDX tag was added in commit
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b24413180f5600bcb3bb70fbed5cf186b60864bd
with the clear title:
"License cleanup: add SPDX GPL-2.0 license identifier to files with no license"
(2017-11-01, by Greg).
Shame on the original contributors for not putting license info in their files...
but I am inclined to believe that they would have been meant to be LGPL,
as the rest of the library and the other plugins.
Could it be that the "everything without a license is GPL" rule
should have exempted libtraceevent?
More importantly, shall we update the three files to be "LGPL-2.1-only" ?
-- zvr
Intel Deutschland GmbH
Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de
Managing Directors: Christin Eisenschmid, Gary Kershaw
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
next reply other threads:[~2019-10-07 17:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-07 17:46 Zavras, Alexios [this message]
2019-10-07 18:16 ` libtraceevent license Greg KH
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=DM5PR1101MB23626F3C7EA8EBA17B2F64DA899B0@DM5PR1101MB2362.namprd11.prod.outlook.com \
--to=alexios.zavras@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-spdx@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;
as well as URLs for NNTP newsgroup(s).