mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Rajat Jain <rajatja@google.com>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>,
	rajatxjain@gmail.com
Subject: Re: [PATCH] Input: input-event-codes.h: Update the deprecated license
Date: Sat, 28 Mar 2020 08:20:31 +0100	[thread overview]
Message-ID: <20200328072031.GA3651219@kroah.com> (raw)
In-Reply-To: <20200328004832.107247-1-rajatja@google.com>

On Fri, Mar 27, 2020 at 05:48:32PM -0700, Rajat Jain wrote:
> >From https://spdx.org/licenses/
> 
> "Release 3.0 replaced previous Identifiers for GNU licenses with more
> explicit Identifiers to reflect the "this version only" or "any later
> version" option specific to those licenses. As such, the previously used
> Identifiers for those licenses are deprecated as of v3.0."
> 
> Replace the
> /* SPDX-License-Identifier: GPL-2.0 WITH Linux-syscall-note */
> with
> /* SPDX-License-Identifier: GPL-2.0-only WITH Linux-syscall-note */
> 
> Signed-off-by: Rajat Jain <rajatja@google.com>

If you like reading documentation for stuff like this, how about reading
LICENSES/preferred/GPL-2.0 which shows that both examples are just fine
and we are going to stick with that for now as we don't want to do a
wholesale change at this point in time.

In other words, we do not follow the 3.0 version of the SPDX spec as we
think it's pretty silly :)

thanks,

greg k-h

  reply	other threads:[~2020-03-28  7:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-28  0:48 Rajat Jain
2020-03-28  7:20 ` Greg Kroah-Hartman [this message]
2020-03-28 20:42   ` Dmitry Torokhov
2020-03-29  7:24     ` Greg Kroah-Hartman
2020-03-29 17:26       ` Rajat Jain

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=20200328072031.GA3651219@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rajatja@google.com \
    --cc=rajatxjain@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

Powered by JetHome