From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Enric Balletbo i Serra <enric.balletbo@collabora.com>
Cc: Andy Shevchenko <andy.shevchenko@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Collabora Kernel ML <kernel@collabora.com>,
groeck@chromium.org, Benson Leung <bleung@chromium.org>,
Dmitry Torokhov <dtor@chromium.org>,
Gwendal Grignou <gwendal@chromium.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Benjamin Tissoires <benjamin.tissoires@redhat.com>,
Bernardo Perez Priego <bernardo.perez.priego@intel.com>,
Daniel Campello <campello@chromium.org>,
Enrico Granata <egranata@chromium.org>,
"Gustavo A. R. Silva" <gustavo@embeddedor.com>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Lee Jones <lee.jones@linaro.org>,
Nick Crews <ncrews@chromium.org>,
Pi-Hsun Shih <pihsun@chromium.org>,
Stephen Boyd <swboyd@chromium.org>,
Wen Yang <wenyang@linux.alibaba.com>,
Yicheng Li <yichengli@chromium.org>
Subject: Re: [PATCH] platform/chrome: Clarify SPDX license with GPL-2.0-only
Date: Fri, 26 Jun 2020 16:11:52 +0200 [thread overview]
Message-ID: <20200626141152.GB4140284@kroah.com> (raw)
In-Reply-To: <6eafe066-ce79-4fad-7a91-c75a564e6663@collabora.com>
On Fri, Jun 26, 2020 at 10:32:55AM +0200, Enric Balletbo i Serra wrote:
> Hi,
>
> On 26/6/20 6:33, Greg Kroah-Hartman wrote:
> > On Thu, Jun 25, 2020 at 10:06:03PM +0300, Andy Shevchenko wrote:
> >> On Thu, Jun 25, 2020 at 9:25 PM Enric Balletbo i Serra
> >> <enric.balletbo@collabora.com> wrote:
> >>>
> >>> Remove the ambiguity with GPL-2.0 and use an explicit GPL-2.0-only
> >>> tag.
> >>
> >> Is there any? Last time IIRC Greg told me that in the kernel the old
> >> and new variants are okay.
> >
> > They are just fine, leave it alone, the in-kernel LICENSES/ files show
> > the valid SPDX tags that the kernel allows at this point in time.
> >
>
> I guess my confusion comes from seeing patch series doing this change in the ML
> instead of really reading the documentation. If it's clear, and as per in-kernel
> docs, it is, that a GPL-2.0 tag is a GPL-2.0 only license, that's fine with me.
It is clear, no churn needed, thanks!
greg k-h
prev parent reply other threads:[~2020-06-26 14:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-25 17:03 Enric Balletbo i Serra
2020-06-25 19:06 ` Andy Shevchenko
2020-06-25 19:29 ` Joe Perches
2020-06-25 19:33 ` Andy Shevchenko
2020-06-25 19:35 ` Andy Shevchenko
2020-06-25 19:52 ` Joe Perches
2020-06-26 10:45 ` Andy Shevchenko
2020-06-25 19:40 ` Joe Perches
2020-06-26 4:33 ` Greg Kroah-Hartman
2020-06-26 8:32 ` Enric Balletbo i Serra
2020-06-26 14:11 ` Greg Kroah-Hartman [this message]
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=20200626141152.GB4140284@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=benjamin.tissoires@redhat.com \
--cc=bernardo.perez.priego@intel.com \
--cc=bleung@chromium.org \
--cc=campello@chromium.org \
--cc=dtor@chromium.org \
--cc=egranata@chromium.org \
--cc=enric.balletbo@collabora.com \
--cc=groeck@chromium.org \
--cc=gustavo@embeddedor.com \
--cc=gwendal@chromium.org \
--cc=kernel@collabora.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ncrews@chromium.org \
--cc=pihsun@chromium.org \
--cc=swboyd@chromium.org \
--cc=wenyang@linux.alibaba.com \
--cc=yichengli@chromium.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®