All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Bartosz Golaszewski <bgolaszewski@baylibre.com>
Cc: Bartosz Golaszewski <brgl@bgdev.pl>,
	Kent Gibson <warthog618@gmail.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	linux-gpio <linux-gpio@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] gpio: uapi: use the preferred SPDX license identifier
Date: Thu, 4 Feb 2021 16:28:56 +0100	[thread overview]
Message-ID: <YBwSuAjNu4FtXSn/@kroah.com> (raw)
In-Reply-To: <CAMpxmJUof3DN2YHBOQm1Z-hrtS1cj6in5CAHowce++36XtqsnA@mail.gmail.com>

On Thu, Feb 04, 2021 at 04:17:51PM +0100, Bartosz Golaszewski wrote:
> On Thu, Feb 4, 2021 at 3:35 PM Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
> >
> > On Thu, Feb 04, 2021 at 03:15:50PM +0100, Bartosz Golaszewski wrote:
> > > On Thu, Feb 4, 2021 at 2:47 PM Greg Kroah-Hartman
> > > <gregkh@linuxfoundation.org> wrote:
> > > >
> > > > On Thu, Feb 04, 2021 at 01:43:57PM +0100, Bartosz Golaszewski wrote:
> > > > > From: Bartosz Golaszewski <bgolaszewski@baylibre.com>
> > > > >
> > > > > GPL-2.0 license identifier is deprecated, let's use the preferred
> > > > > identifier: GPL-2.0-only.
> > > > >
> > > > > Signed-off-by: Bartosz Golaszewski <bgolaszewski@baylibre.com>
> > > > > ---
> > > > > Hi Kent, Greg,
> > > > >
> > > > > I started working on making libgpiod licensing reuse-compliant and noticed
> > > > > that the reuse-tool is telling me that the GPL-2.0 SPDX identifier in the
> > > > > GPIO uapi header is deprecated. Since I'm required to copy the header
> > > > > verbatim into libgpiod's repository, I think we need to fix that at source
> > > > > first.
> > > > >
> > > > >  include/uapi/linux/gpio.h | 2 +-
> > > > >  1 file changed, 1 insertion(+), 1 deletion(-)
> > > > >
> > > > > diff --git a/include/uapi/linux/gpio.h b/include/uapi/linux/gpio.h
> > > > > index e4eb0b8c5cf9..3e01ededbf36 100644
> > > > > --- a/include/uapi/linux/gpio.h
> > > > > +++ b/include/uapi/linux/gpio.h
> > > > > @@ -1,4 +1,4 @@
> > > > > -/* SPDX-License-Identifier: GPL-2.0 WITH Linux-syscall-note */
> > > > > +/* SPDX-License-Identifier: GPL-2.0-only WITH Linux-syscall-note */
> > > >
> > > > No, there is no need to convert the kernel to the "latest" spdx level,
> > > > when we started out there was no "-only" nonsense (hint no other license
> > > > has that crud), and "GPL-2.0" is a totally valid summary of the license.
> > > >
> > > > So please don't go changing it all in-kernel, that way lies madness.
> > > > Let's finish fixing up ALL kernel files before worrying about what SPDX
> > > > "version" we are at.
> > > >
> > >
> > > But then, the reuse script is telling me:
> > >
> > >     Unfortunately, your project is not compliant with version 3.0 of
> > > the REUSE Specification :-(
> > >
> > > because I'm using a deprecated license. :(
> >
> > Go yell at the REUSE people, there's no requirement to have the most
> > recent version of SPDX, is there?   :)
> >
> > And if that's the only thing wrong with the project when running 'reuse
> > lint' then you should be happy, no one will complain at all.
> >
> > thanks,
> >
> > greg k-h
> 
> Ok, I get it but let me try one last time: there's absolutely no harm
> in merging this patch for the next release, is there? Currently there
> are around 15000 instances of "GPL-2.0-only" in the kernel vs 30000
> "GPL-2.0" - so the former is not that uncommon.

It's up to the owner/maintainer of this file in the end, but I don't
want to see patches doing this for many more files, as it's pointless
churn as far as the kernel is concerned.

thanks,

greg k-h

  reply	other threads:[~2021-02-04 15:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-04 12:43 [PATCH] gpio: uapi: use the preferred SPDX license identifier Bartosz Golaszewski
2021-02-04 13:47 ` Greg Kroah-Hartman
2021-02-04 14:15   ` Bartosz Golaszewski
2021-02-04 14:35     ` Greg Kroah-Hartman
2021-02-04 15:17       ` Bartosz Golaszewski
2021-02-04 15:28         ` Greg Kroah-Hartman [this message]
2021-02-10 13:05           ` Bartosz Golaszewski

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=YBwSuAjNu4FtXSn/@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=bgolaszewski@baylibre.com \
    --cc=brgl@bgdev.pl \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=warthog618@gmail.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 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.