From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Christoph Hellwig <hch@lst.de>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Hannes Reinecke <hare@suse.com>
Subject: Re: linux-next: manual merge of the scsi tree with Linus' tree
Date: Thu, 20 Jun 2019 21:14:07 -0400 [thread overview]
Message-ID: <yq1fto3pwo0.fsf@oracle.com> (raw)
In-Reply-To: <1561077341.7970.47.camel@HansenPartnership.com> (James Bottomley's message of "Thu, 20 Jun 2019 17:35:41 -0700")
James,
> There's two problems. One is simple terminology: the
> Documentation/process/licence-rules.rst say:
>
> GPL-2.0 means GPL 2 only
> GPL-2.0+ means GPL 2 or later
>
> I believe RMS made a fuss about this and he finally agreed to
>
> GPL-2.0-only
> GPL-2.0-or-later
Looks like there are tons of the old style SPDX tags in the kernel. Is
there going to be a treewide conversion to the new tag format?
Just wondering how much to clean up given that the files Christoph
touched only constitute a subset of the old style tags found under
drivers/scsi.
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2019-06-21 1:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-22 0:08 linux-next: manual merge of the scsi tree with Linus' tree Stephen Rothwell
2019-05-28 1:43 ` Stephen Rothwell
2019-06-20 23:59 ` Stephen Rothwell
2019-06-21 0:07 ` Linus Torvalds
2019-06-21 0:34 ` Martin K. Petersen
2019-06-21 0:35 ` James Bottomley
2019-06-21 0:47 ` Linus Torvalds
2019-06-21 1:14 ` Martin K. Petersen [this message]
2019-06-21 6:21 ` Greg Kroah-Hartman
-- strict thread matches above, loose matches on Subject: below --
2019-05-22 0:11 Stephen Rothwell
2019-01-24 3:58 Stephen Rothwell
2019-01-14 2:48 Stephen Rothwell
2019-01-14 5:42 ` 黃清隆
2017-11-06 3:48 Stephen Rothwell
[not found] <20140124130547.323ce38edc8dedfd653534b7@canb.auug.org.au>
2014-01-24 2:22 ` James Bottomley
2012-07-20 0:32 Stephen Rothwell
2012-07-20 7:29 ` James Bottomley
2012-07-20 16:31 ` Linus Torvalds
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=yq1fto3pwo0.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=gregkh@linuxfoundation.org \
--cc=hare@suse.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.