From: Hans de Goede <hdegoede@redhat.com>
To: Philippe Ombredanne <pombredanne@nexb.com>
Cc: Darren Hart <dvhart@infradead.org>,
Andy Shevchenko <andy@infradead.org>,
platform-driver-x86@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>, James <james@panaceas.org>
Subject: Re: [PATCH] platform/x86: Add driver for GPD pocket custom fan controller
Date: Tue, 12 Dec 2017 17:39:18 +0100 [thread overview]
Message-ID: <7e78fc7d-b837-6b8c-55cc-799cca9b9fc2@redhat.com> (raw)
In-Reply-To: <CAOFm3uE540=Y=pgz=tcM2djQVYZw5b8uOP5wQwJNNhCNEXuW=g@mail.gmail.com>
Hi,
On 12-12-17 16:33, Philippe Ombredanne wrote:
> Dear Hans,
>
> On Tue, Dec 12, 2017 at 4:11 PM, Hans de Goede <hdegoede@redhat.com> wrote:
>> Add a driver for the GPD pocket device's custom fan controller, which
>> gets controlled through 2 GPIOs listed in a FAN02501 ACPI device.
> [...]
>
>> --- /dev/null
>> +++ b/drivers/platform/x86/gpd-pocket-fan.c
>> @@ -0,0 +1,193 @@
>> +/* SPDX-License-Identifier: GPL-2.0 */
>
> This should be IMHO this style as requested by Linus on list and
> documented by Thomas in the doc patches:
> // SPDX-License-Identifier: GPL-2.0
Ok, fixed for v2.
>> +MODULE_LICENSE("GPL");
>
> This module license means "GPL 2 or later" and does not match your top
> level GPL 2.0 license tag and should be instead as per module.h doc:
> MODULE_LICENSE("GPL v2");
>
> .... unless you want this to be GPL 2.0 or later all the way in which
> case it should be:
> // SPDX-License-Identifier: GPL-2.0+
> and
> MODULE_LICENSE("GPL");
>
> ... though I am not sure what is the point of "or later" for a module.
I prefer for "v2 or later" just in case there ever is a GPL v4
which is more sensible then v3...
So I've changed the SPDX identifier to:
// SPDX-License-Identifier: GPL-2.0+
Regards,
Hans
prev parent reply other threads:[~2017-12-12 16:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-12 15:11 Hans de Goede
2017-12-12 15:33 ` Philippe Ombredanne
2017-12-12 16:39 ` Hans de Goede [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=7e78fc7d-b837-6b8c-55cc-799cca9b9fc2@redhat.com \
--to=hdegoede@redhat.com \
--cc=andy@infradead.org \
--cc=dvhart@infradead.org \
--cc=james@panaceas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=pombredanne@nexb.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 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®