From: Jacek Anaszewski <jacek.anaszewski@gmail.com>
To: Daniel Mack <daniel@zonque.org>, robh+dt@kernel.org
Cc: linux-leds@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v4 5/5] leds: lt3593: update email address and switch to SPDX license header
Date: Fri, 22 Jun 2018 23:56:40 +0200 [thread overview]
Message-ID: <42bb7da0-3a5f-48e5-b12c-332307c794f3@gmail.com> (raw)
In-Reply-To: <20180621202322.11581-6-daniel@zonque.org>
Hi Daniel,
Thanks for sorting the things out.
Patch set applied to the for-next branch of linux-leds.git
I have one more remark while we are at it, please refer below.
On 06/21/2018 10:23 PM, Daniel Mack wrote:
> Update the email address in the module information and in the comments
> and in the module information, and drop the existing boilerplate in
> favor of a SPDX header.
>
> Signed-off-by: Daniel Mack <daniel@zonque.org>
> ---
> drivers/leds/leds-lt3593.c | 21 +++------------------
> 1 file changed, 3 insertions(+), 18 deletions(-)
>
> diff --git a/drivers/leds/leds-lt3593.c b/drivers/leds/leds-lt3593.c
> index b9a907e9d321..f6aae616242e 100644
> --- a/drivers/leds/leds-lt3593.c
> +++ b/drivers/leds/leds-lt3593.c
> @@ -1,20 +1,5 @@
> -/*
> - * LEDs driver for LT3593 controllers
> - *
> - * See the datasheet at http://cds.linear.com/docs/Datasheet/3593f.pdf
> - *
> - * Copyright (c) 2009 Daniel Mack <daniel@caiaq.de>
> - *
> - * Based on leds-gpio.c,
> - *
> - * Copyright (C) 2007 8D Technologies inc.
> - * Raphael Assenat <raph@8d.com>
> - * Copyright (C) 2008 Freescale Semiconductor, Inc.
> - *
> - * This program is free software; you can redistribute it and/or modify
> - * it under the terms of the GNU General Public License version 2 as
> - * published by the Free Software Foundation.
> - */
> +// SPDX-License-Identifier: GPL-2.0
> +// Copyright (c) 2009,2018 Daniel Mack <daniel@zonque.org>
>
> #include <linux/kernel.h>
> #include <linux/platform_device.h>
> @@ -215,7 +200,7 @@ static struct platform_driver lt3593_led_driver = {
>
> module_platform_driver(lt3593_led_driver);
>
> -MODULE_AUTHOR("Daniel Mack <daniel@caiaq.de>");
> +MODULE_AUTHOR("Daniel Mack <daniel@zonque.org>");
> MODULE_DESCRIPTION("LED driver for LT3593 controllers");
> MODULE_LICENSE("GPL");
I've just noticed the pre-existing discrepancy between the license
message (GPL v2) and MODULE_LICENSE("GPL"). Is there a reason to keep
it that way?
> MODULE_ALIAS("platform:leds-lt3593");
>
--
Best regards,
Jacek Anaszewski
next prev parent reply other threads:[~2018-06-22 21:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-21 20:23 [PATCH v4 0/5] leds: add devicetree functionality to lltc,lt3593 driver Daniel Mack
2018-06-21 20:23 ` [PATCH v4 1/5] dt-bindings: leds: Add bindings for lltc,lt3593 Daniel Mack
2018-06-25 15:59 ` Rob Herring
2018-06-25 20:21 ` Daniel Mack
2018-06-21 20:23 ` [PATCH v4 2/5] leds: lt3593: merge functions and clean up code Daniel Mack
2018-06-21 20:23 ` [PATCH v4 3/5] leds: lt3593: switch to gpiod interface Daniel Mack
2018-06-21 20:23 ` [PATCH v4 4/5] leds: lt3593: Add device tree probing glue Daniel Mack
2018-06-21 20:23 ` [PATCH v4 5/5] leds: lt3593: update email address and switch to SPDX license header Daniel Mack
2018-06-22 21:56 ` Jacek Anaszewski [this message]
2018-06-23 19:52 ` Daniel Mack
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=42bb7da0-3a5f-48e5-b12c-332307c794f3@gmail.com \
--to=jacek.anaszewski@gmail.com \
--cc=daniel@zonque.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=robh+dt@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).