mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Charlemagne Lasse <charlemagnelasse@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	"Thomas Gleixner" <tglx@linutronix.de>,
	"Basil Peace" <grv87@yandex.ru>,
	"Carmen Bianca Bakker" <carmen@carmenbianca.eu>,
	"Keith Maxwell" <keith.maxwell@gmail.com>,
	"Matija Šuklje" <matija.suklje@liferay.com>
Subject: Re: REUSE/SPDX: Invalid LicenseRef in Linux sources
Date: Fri, 9 Aug 2019 11:43:03 +0200	[thread overview]
Message-ID: <20190809094303.GA6297@kroah.com> (raw)
In-Reply-To: <CAFGhKbwJVv23Mwd7ruo8JCC-0U3BdNRwnxih9zgFSCyPe=jnoA@mail.gmail.com>

On Fri, Aug 09, 2019 at 11:30:44AM +0200, Charlemagne Lasse wrote:
> When I run the reuse lint tool on the current linux sources, I get
> following error
> 
> reuse.project - WARNING - Could not resolve SPDX identifier of
> LICENSES/deprecated/GPL-1.0, resolving to LicenseRef-Unknown0
> reuse.project - WARNING - Could not resolve SPDX identifier of
> LICENSES/exceptions/GCC-exception-2.0, resolving to
> LicenseRef-Unknown1
> reuse.project - WARNING - Could not resolve SPDX identifier of
> LICENSES/preferred/LGPL-2.0, resolving to LicenseRef-Unknown2
> reuse.project - WARNING - Could not resolve SPDX identifier of
> LICENSES/preferred/LGPL-2.1, resolving to LicenseRef-Unknown3
> reuse.project - WARNING - Could not resolve SPDX identifier of
> LICENSES/preferred/GPL-2.0, resolving to LicenseRef-Unknown4
> reuse.project - WARNING - Could not resolve SPDX identifier of
> LICENSES/dual/Apache-2.0, resolving to LicenseRef-Unknown5
> reuse.project - WARNING - Could not resolve SPDX identifier of
> LICENSES/dual/MPL-1.1, resolving to LicenseRef-Unknown6
> reuse.project - WARNING - Could not resolve SPDX identifier of
> LICENSES/dual/CDDL-1.0, resolving to LicenseRef-Unknown7
> 
> Can you please help to fix the problem

Please fix the reuse tool, I don't see this being a kernel issue, it has
never said it follows the spec put forth by the reuse project.

thanks,

greg k-h

  reply	other threads:[~2019-08-09  9:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-09  9:30 Charlemagne Lasse
2019-08-09  9:43 ` Greg Kroah-Hartman [this message]
2019-08-09 12:14 ` Carmen Bianca Bakker

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=20190809094303.GA6297@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=carmen@carmenbianca.eu \
    --cc=charlemagnelasse@gmail.com \
    --cc=grv87@yandex.ru \
    --cc=keith.maxwell@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matija.suklje@liferay.com \
    --cc=tglx@linutronix.de \
    /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