From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: Enric Balletbo i Serra <enric.balletbo@collabora.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Gwendal Grignou <gwendal@chromium.org>,
kernel@collabora.com, linux-input@vger.kernel.org
Subject: Re: [PATCH v2 5/8] Input: cros_ec_keyb - Switch to SPDX identifier.
Date: Tue, 5 Jun 2018 11:29:19 -0700 [thread overview]
Message-ID: <20180605182919.GF202428@dtor-ws> (raw)
In-Reply-To: <CAOMZO5Cod=jo5gC1ibQx5ZHU5xtUZDvfZt899=nPLgH4bhy+_g@mail.gmail.com>
On Tue, Jun 05, 2018 at 03:16:40PM -0300, Fabio Estevam wrote:
> Hi Enric,
>
> On Tue, Jun 5, 2018 at 3:14 PM, Enric Balletbo i Serra
> <enric.balletbo@collabora.com> wrote:
>
> > 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.
>
> Ok, but I think you should add this explanation in the commit log to
> make it clearer.
If there is a conflict between the license notice and MODULE_LICENSE()
we should go by the license notice. The license note is usually approved
by companies, whereas MIODULE_LICENSE()s get moved, adjusted, etc.
For ChromeOS kernel changes license notice is GPL v2 as documented at:
https://www.chromium.org/chromium-os/how-tos-and-troubleshooting/kernel-faq
section "Which copyright header should I use?"
Thanks.
--
Dmitry
next prev parent reply other threads:[~2018-06-05 18:29 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 [this message]
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
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=20180605182919.GF202428@dtor-ws \
--to=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.