From: Mauro Carvalho Chehab <mchehab@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Lukas Bulwahn <lukas.bulwahn@gmail.com>,
Cai Huoqing <caihuoqing@baidu.com>,
linux-media@vger.kernel.org, Thomas Gleixner <tglx@linutronix.de>,
linux-spdx@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] media: prefer generic SPDX-License expression to deprecated one
Date: Thu, 16 Dec 2021 13:15:22 +0100 [thread overview]
Message-ID: <20211216131522.4e7b148d@coco.lan> (raw)
In-Reply-To: <Ybsrdll5sqIakINT@kroah.com>
Em Thu, 16 Dec 2021 13:05:10 +0100
Greg Kroah-Hartman <gregkh@linuxfoundation.org> escreveu:
> On Thu, Dec 16, 2021 at 12:23:11PM +0100, Mauro Carvalho Chehab wrote:
> > Em Thu, 16 Dec 2021 11:31:32 +0100
> > Lukas Bulwahn <lukas.bulwahn@gmail.com> escreveu:
> >
> > > Commit 8d395ce6f04b ("media: dvb-core: Convert to SPDX identifier") and
> > > commit e67219b0496b ("media: b2c2: flexcop: Convert to SPDX identifier")
> > > introduce the SPDX-License expression LGPL-2.1-or-later for some files.
> > >
> > > The command ./scripts/spdxcheck.py warns:
> > >
> > > drivers/media/dvb-core/dmxdev.c: 1:28 Invalid License ID: LGPL-2.1-or-later
> > > drivers/media/dvb-core/dvb_demux.c: 1:28 Invalid License ID: LGPL-2.1-or-later
> > > drivers/media/dvb-core/dvbdev.c: 1:28 Invalid License ID: LGPL-2.1-or-later
> > > drivers/media/common/b2c2/flexcop.c: 1:28 Invalid License ID: LGPL-2.1-or-later
> > >
> > > The preferred SPDX expression for LGPL-2.1 or any later version is with
> > > the more generic "+"-extension for "any later version", so: LGPL-2.1+
> > >
> > > This makes spdxcheck happy again.
> >
> > It doesn't sound right to apply such patch.
> >
> > See, the latest SPDX version uses LGPL-2.1-or-later:
> >
> > https://spdx.org/licenses/LGPL-2.1-or-later.html
> >
> > And it deprecated LGPL-2.1+:
> >
> > https://spdx.org/licenses/LGPL-2.1+.html
> >
> > So, those files are perfectly fine with regards to SPDX, and are
> > adherent to its latest specs. We do need the latest specs on media,
> > as our documentation is under GFDL-1.1-no-invariants-or-later, which
> > only exists on newer SPDX versions.
> >
> > So, the right thing to do here seems to fix spdxcheck.py, letting it
> > either allow both variants (as we probably don't want to replace it
> > everywhere) or to emit a warning if the deprecated ones are used.
>
> No, we are not going to add a "warning" for older SPDX versions like
> that, otherwise the majority of the kernel will start spitting out
> warnings.
>
> Let's worry about actually fixing all of the files that do NOT have SPDX
> tags before even considering to move to a newer version of the spec. We
> started this work before the FSF made the crazy change to their tags,
> let's not worry about any deprecated issues at the moment.
Yeah, agreed.
Thanks,
Mauro
next prev parent reply other threads:[~2021-12-16 12:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-16 10:31 [PATCH] media: prefer generic SPDX-License expression to deprecated one Lukas Bulwahn
2021-12-16 10:48 ` Cai Huoqing
2021-12-16 11:23 ` Mauro Carvalho Chehab
2021-12-16 11:32 ` [PATCH] LICENSES/LGPL-2.1: Add LGPL-2.1-or-later as valid identifiers Mauro Carvalho Chehab
2021-12-16 11:33 ` [PATCH v2] " Mauro Carvalho Chehab
2021-12-16 12:06 ` Greg Kroah-Hartman
2021-12-16 12:05 ` [PATCH] media: prefer generic SPDX-License expression to deprecated one Greg Kroah-Hartman
2021-12-16 12:15 ` Mauro Carvalho Chehab [this message]
2021-12-16 13:17 ` Lukas Bulwahn
2021-12-16 12:07 ` Greg Kroah-Hartman
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=20211216131522.4e7b148d@coco.lan \
--to=mchehab@kernel.org \
--cc=caihuoqing@baidu.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-spdx@vger.kernel.org \
--cc=lukas.bulwahn@gmail.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