From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Cc: Cai Huoqing <caihuoqing@baidu.com>,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-spdx@vger.kernel.org
Subject: Re: [PATCH v3] LICENSES/LGPL-2.1: Add LGPL-2.1-or-later as valid identifiers
Date: Thu, 16 Dec 2021 14:30:47 +0100 [thread overview]
Message-ID: <Ybs/h3WAY3FFVC4/@kroah.com> (raw)
In-Reply-To: <CAKXUXMwsxiUncxS4Fip=7iK-xrUZSXY61jNcO61bgMyQ0DYp6A@mail.gmail.com>
On Thu, Dec 16, 2021 at 02:28:10PM +0100, Lukas Bulwahn wrote:
> On Thu, Dec 16, 2021 at 2:17 PM Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
> >
> > On Thu, Dec 16, 2021 at 08:30:14PM +0800, Cai Huoqing wrote:
> > > On 16 12月 21 13:17:35, Mauro Carvalho Chehab wrote:
> > > > Some files have been flagged with the new LGPL-2.1-or-later
> > > > identifier which replace the original LGPL-2.1+ in the SPDX license
> > > > identifier specification, but the identifiers are not mentioned as
> > > > valid in the LGPL-2.1 license file.
> > > >
> > > > Add it, together with the LGPL-2.1-only at the the license file.
> > > >
> > > > Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
> > > > ---
> > > > LICENSES/preferred/LGPL-2.1 | 2 ++
> > > > 1 file changed, 2 insertions(+)
> > > >
> > > > diff --git a/LICENSES/preferred/LGPL-2.1 b/LICENSES/preferred/LGPL-2.1
> > > > index 27bb4342a3e8..b73f9b6230f5 100644
> > > > --- a/LICENSES/preferred/LGPL-2.1
> > > > +++ b/LICENSES/preferred/LGPL-2.1
> > > > @@ -1,5 +1,7 @@
> > > > Valid-License-Identifier: LGPL-2.1
> > > > +Valid-License-Identifier: LGPL-2.1-only
> > > > Valid-License-Identifier: LGPL-2.1+
> > > > +Valid-License-Identifier: LGPL-2.1-or-later
> > > > SPDX-URL: https://spdx.org/licenses/LGPL-2.1.html
> > > The URL is deprecated, do we need to update it together.
> >
> > No.
> >
> > > The same, GPL-2.0, LGPL-2.0
> >
> > Again, no. We are using an older version of the SPDX specification,
> > this is fine.
> >
>
> Mauro's patch just makes sure that spdxcheck.py does not complain
> about the SPDX License Identifiers from SPDX spec v2 and from v3. It
> really does not deprecate anything or implies that everything in the
> kernel needs to move to v3 (which might really be some crazy
> disturbing refactoring effort without a lot of gain), but it allows
> developers that want to use the tags from SPDX spec v3 can do so.
>
> I would assume making the kernel/a tool in the kernel supporting
> something more while being backwards-compatible is the standard way we
> work... So, Greg, this patch is fine to be included, right?
Yes, this patch is fine, I will queue it up in a bit, thanks!
greg k-h
prev parent reply other threads:[~2021-12-16 13:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-16 12:17 [PATCH v3] LICENSES/LGPL-2.1: Add LGPL-2.1-or-later as valid identifiers Mauro Carvalho Chehab
2021-12-16 12:30 ` Cai Huoqing
2021-12-16 13:17 ` Greg Kroah-Hartman
2021-12-16 13:28 ` Lukas Bulwahn
2021-12-16 13:30 ` Greg Kroah-Hartman [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:
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=Ybs/h3WAY3FFVC4/@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=caihuoqing@baidu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spdx@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=mchehab+huawei@kernel.org \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).