LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org, linux-spdx@vger.kernel.org
Subject: Re: [GIT PULL] SPDX update for 5.2-rc1 - round 1
Date: Wed, 29 May 2019 15:13:00 +0200 [thread overview]
Message-ID: <20190529131300.GV3274@piout.net> (raw)
In-Reply-To: <20190521133257.GA21471@kroah.com>
Hello,
On 21/05/2019 15:32:57+0200, Greg KH wrote:
> - Add GPL-2.0-only or GPL-2.0-or-later tags to files where our scan
I'm very confused by those two tags because they are not mentioned in
the SPDX 2.1 specification or the kernel documentation and seem to just
be from https://spdx.org/ids-howi which doesn't seem to be versionned
anywhere.
While I understand the rationale behind those, I believe the correct way
of introducing them would be first to add them in the spec and
documentation and then make use of them.
Now, what should we do with all the GPL-2.0 and GPL-2.0+ tags that we
have?
--
Alexandre Belloni, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-05-29 13:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-21 13:32 Greg KH
2019-05-21 19:55 ` pr-tracker-bot
2019-05-21 19:56 ` Linus Torvalds
2019-05-22 16:34 ` Greg KH
2019-05-22 4:32 ` Masahiro Yamada
2019-05-22 6:34 ` Joe Perches
2019-05-22 10:14 ` Thomas Gleixner
2019-05-23 2:49 ` Masahiro Yamada
2019-05-23 2:57 ` Joe Perches
2019-05-23 5:33 ` Thomas Gleixner
2019-06-25 11:19 ` Masahiro Yamada
2019-05-29 13:13 ` Alexandre Belloni [this message]
2019-05-29 13:51 ` Thomas Gleixner
2019-05-29 14:16 ` Zavras, Alexios
[not found] ` <B03F305C-F579-43E1-BEE7-D628BD44FF48@jilayne.com>
2019-05-31 0:25 ` J Lovejoy
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=20190529131300.GV3274@piout.net \
--to=alexandre.belloni@bootlin.com \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spdx@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--subject='Re: [GIT PULL] SPDX update for 5.2-rc1 - round 1' \
/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
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).