Linux-SPDX Archive on
 help / color / Atom feed
From: Greg KH <>
To: "Zavras, Alexios" <>
Cc: "" <>
Subject: Re: libtraceevent  license
Date: Mon, 7 Oct 2019 20:16:30 +0200
Message-ID: <> (raw)
In-Reply-To: <>

On Mon, Oct 07, 2019 at 05:46:58PM +0000, Zavras, Alexios wrote:
> 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 
> 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
> 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?

If you wish to have it changed, please talk to the owners of those files
and everyone who submitted patches to them.

> More importantly, shall we update the three files to be "LGPL-2.1-only" ?

Sorry, if a file did not have a license specified in it, then it fell
under the default license for the kernel.


greg k-h

      reply index

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-07 17:46 Zavras, Alexios
2019-10-07 18:16 ` Greg KH [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Linux-SPDX Archive on

Archives are clonable:
	git clone --mirror linux-spdx/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-spdx linux-spdx/ \
	public-inbox-index linux-spdx

Example config snippet for mirrors

Newsgroup available over NNTP:

AGPL code for this site: git clone