From: Linus Torvalds <torvalds@linux-foundation.org>
To: Paul Burton <paul.burton@mips.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mips@vger.kernel.org" <linux-mips@vger.kernel.org>
Subject: Re: [GIT PULL] MIPS changes
Date: Wed, 17 Jul 2019 09:41:49 -0700 [thread overview]
Message-ID: <CAHk-=wipjStEwJj2_iWxBdVC4oV8rY5NjrRb1tmWLUa0VrS_Eg@mail.gmail.com> (raw)
In-Reply-To: <20190717152545.bhdnhjdf2tlhuv3o@pburton-laptop>
On Wed, Jul 17, 2019 at 8:25 AM Paul Burton <paul.burton@mips.com> wrote:
>
> Documentation/process/license-rules.rst suggests to me that the version
> in the MIPS tree is correct in terms of license name ("GPL-2.0" without
> the "-only" suffix) whilst the version in master is correct in terms of
> comment style ("/* */" rather than "//").
It's actually license-rules.rst that just hasn't been updated. The
"GPL-.2.0" and "GPL-2.0+" naming was considered too terse, so the
modern spdx tag suggestions are "GPL-2.0-only" and "GPL-2.0-or-later".
The full list of all spdx license tags (many of which aren't relevant
for the kernel, of course) can be found at
https://spdx.org/licenses/
in case you care.
Linus
next prev parent reply other threads:[~2019-07-17 16:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-17 15:25 [GIT PULL] MIPS changes Paul Burton
2019-07-17 16:41 ` Linus Torvalds [this message]
2019-07-17 16:50 ` pr-tracker-bot
2019-09-21 23:10 Paul Burton
2019-09-22 16:45 ` pr-tracker-bot
2019-09-22 18:35 ` Linus Torvalds
2019-09-23 15:36 ` Florian Fainelli
2019-09-23 18:07 ` Paul Burton
2019-09-23 18:18 ` Linus Torvalds
2019-09-24 12:40 ` David Howells
2019-09-24 15:32 ` Linus Torvalds
2020-01-31 17:55 Paul Burton
2020-01-31 19:35 ` pr-tracker-bot
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='CAHk-=wipjStEwJj2_iWxBdVC4oV8rY5NjrRb1tmWLUa0VrS_Eg@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=paul.burton@mips.com \
/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).