All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Enric Balletbo i Serra <enric.balletbo@collabora.com>
Cc: Fabio Estevam <festevam@gmail.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Gwendal Grignou <gwendal@chromium.org>,
	kernel@collabora.com, Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	linux-input@vger.kernel.org
Subject: Re: [PATCH v2 5/8] Input: cros_ec_keyb - Switch to SPDX identifier.
Date: Mon, 25 Jun 2018 14:42:32 +0800	[thread overview]
Message-ID: <20180625064232.GB4233@kroah.com> (raw)
In-Reply-To: <5926a3f2-3646-f9e1-619a-255e619f41f0@collabora.com>

On Mon, Jun 25, 2018 at 08:23:38AM +0200, Enric Balletbo i Serra wrote:
> Hi Grek,
> 
> On 25/06/18 03:57, Greg KH wrote:
> > On Tue, Jun 05, 2018 at 08:14:24PM +0200, Enric Balletbo i Serra wrote:
> >> Hi Fabio,
> >>
> >> On 05/06/18 20:04, Fabio Estevam wrote:
> >>> Hi Enric,
> >>>
> >>> On Tue, Jun 5, 2018 at 2:54 PM, Enric Balletbo i Serra
> >>> <enric.balletbo@collabora.com> wrote:
> >>>> Adopt the SPDX license identifier headers to ease license compliance
> >>>> management.
> >>>>
> >>>> Signed-off-by: Enric Balletbo i Serra <enric.balletbo@collabora.com>
> >>>> ---
> >>>>
> >>>> Changes in v2:
> >>>> - [6/9] Do not remove last paragraph.
> >>>>
> >>>>  drivers/input/keyboard/cros_ec_keyb.c | 34 ++++++++++-----------------
> >>>>  1 file changed, 12 insertions(+), 22 deletions(-)
> >>>>
> >>>> diff --git a/drivers/input/keyboard/cros_ec_keyb.c b/drivers/input/keyboard/cros_ec_keyb.c
> >>>> index 79eb29550c34..91b2839c12df 100644
> >>>> --- a/drivers/input/keyboard/cros_ec_keyb.c
> >>>> +++ b/drivers/input/keyboard/cros_ec_keyb.c
> >>>> @@ -1,25 +1,15 @@
> >>>> -/*
> >>>> - * ChromeOS EC keyboard driver
> >>>> - *
> >>>> - * Copyright (C) 2012 Google, Inc
> >>>> - *
> >>>> - * This software is licensed under the terms of the GNU General Public
> >>>> - * License version 2, as published by the Free Software Foundation, and
> >>>
> >>> Original text says GPL-2.0...
> >>>
> >>>> - * may be copied, distributed, and modified under those terms.
> >>>> - *
> >>>> - * This program is distributed in the hope that it will be useful,
> >>>> - * but WITHOUT ANY WARRANTY; without even the implied warranty of
> >>>> - * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
> >>>> - * GNU General Public License for more details.
> >>>> - *
> >>>> - * This driver uses the Chrome OS EC byte-level message-based protocol for
> >>>> - * communicating the keyboard state (which keys are pressed) from a keyboard EC
> >>>> - * to the AP over some bus (such as i2c, lpc, spi).  The EC does debouncing,
> >>>> - * but everything else (including deghosting) is done here.  The main
> >>>> - * motivation for this is to keep the EC firmware as simple as possible, since
> >>>> - * it cannot be easily upgraded and EC flash/IRAM space is relatively
> >>>> - * expensive.
> >>>> - */
> >>>> +// SPDX-License-Identifier: GPL-2.0+
> >>>
> >>> but here you add a GPL-2.0+ type.
> >>>
> >>
> >> Right, but the module license is set to GPL which means GNU Public License v2 or
> >> later, see [1]. So, there is a mismatch. In such cases I assumed GPL-2.0+ as the
> >> default. These mismatches are common so I think that should be fine for the
> >> authors, if someone is disagree just let me know and I will change.
> > 
> > NO!
> > 
> > The license text is what you need to follow as almost everyone gets the
> > MODULE_LICENSE() stuff wrong.  You can not follow the MODULE_LICENSE
> > marking for determining GPLv2 vs. GPLv2+ at this point in time.  After
> > we get the SPDX stuff all cleaned up then we can go and fix up the
> > MODULE_LICENSE mismatch.
> > 
> > So again, always defer to the license text in the file, NOT the
> > MODULE_LICENSE() marking.
> > 
> 
> Many thanks for your feedback, Dmitry already told me that I was doing wrong
> this and I sent another version following the license text, so this patchset was
> superseded for v3 [1].
> 
> [1] https://patchwork.ozlabs.org/cover/925906/

Ah, good, sorry for the noise then, I didn't see that series.

greg k-h

  reply	other threads:[~2018-06-25  6:42 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-05 17:54 [PATCH v2 0/8] cros_ec: Switch to SPDX identifier Enric Balletbo i Serra
2018-06-05 17:54 ` Enric Balletbo i Serra
2018-06-05 17:54 ` [PATCH v2 1/8] platform/chrome: " Enric Balletbo i Serra
2018-06-05 20:51   ` Benson Leung
2018-06-05 17:54 ` [PATCH v2 2/8] platform/chrome: pstore: " Enric Balletbo i Serra
2018-06-05 20:54   ` Benson Leung
2018-06-05 17:54 ` [PATCH v2 3/8] mfd: cros_ec: Add or fix SPDX-License-Identifier in all files Enric Balletbo i Serra
2018-06-18  6:37   ` Lee Jones
2018-06-19  9:05     ` Enric Balletbo i Serra
2018-06-05 17:54 ` [PATCH v2 4/8] iio: cros_ec: Switch to SPDX identifier Enric Balletbo i Serra
2018-06-05 17:54 ` [PATCH v2 5/8] Input: cros_ec_keyb - " Enric Balletbo i Serra
2018-06-05 18:04   ` Fabio Estevam
2018-06-05 18:14     ` Enric Balletbo i Serra
2018-06-05 18:16       ` Fabio Estevam
2018-06-05 18:29         ` Dmitry Torokhov
2018-06-05 18:45           ` Enric Balletbo i Serra
2018-06-05 18:52             ` Dmitry Torokhov
2018-06-25  1:57       ` Greg KH
2018-06-25  6:23         ` Enric Balletbo i Serra
2018-06-25  6:42           ` Greg KH [this message]
2018-06-05 17:54 ` [PATCH v2 6/8] pwm: cros-ec: " Enric Balletbo i Serra
2018-06-06  9:08   ` Thierry Reding
2018-06-06  9:21     ` Enric Balletbo i Serra
2018-06-06  9:43       ` Thierry Reding
2018-07-09 17:02   ` Thierry Reding
2018-06-05 17:54 ` [PATCH v2 7/8] extcon: usbc-cros-ec: " Enric Balletbo i Serra
2018-06-05 18:15   ` Benson Leung
2018-06-05 18:43     ` Dmitry Torokhov
2018-06-05 17:54 ` [PATCH v2 8/8] i2c: i2c-cros-ec-tunnel: " Enric Balletbo i Serra

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=20180625064232.GB4233@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=enric.balletbo@collabora.com \
    --cc=festevam@gmail.com \
    --cc=gwendal@chromium.org \
    --cc=kernel@collabora.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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.