From: Bartosz Golaszewski <brgl@bgdev.pl>
To: Keguang Zhang <keguang.zhang@gmail.com>
Cc: linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Subject: Re: [PATCH v2 1/5] gpio: loongson1: Convert to SPDX identifier
Date: Mon, 6 Mar 2023 10:29:23 +0100 [thread overview]
Message-ID: <CAMRc=Me=Yrr5BuRaMd4r91URzmdYHWUvVGvLL9YFuZPaV0WYFA@mail.gmail.com> (raw)
In-Reply-To: <20230302125215.214014-2-keguang.zhang@gmail.com>
On Thu, Mar 2, 2023 at 1:52 PM Keguang Zhang <keguang.zhang@gmail.com> wrote:
>
> Use SPDX-License-Identifier instead of the license text and
> update the author information.
>
> Signed-off-by: Keguang Zhang <keguang.zhang@gmail.com>
> ---
> V1 -> V2: Keep GPLv2, just convert to SPDX identifier
> ---
> drivers/gpio/gpio-loongson1.c | 9 +++------
> 1 file changed, 3 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/gpio/gpio-loongson1.c b/drivers/gpio/gpio-loongson1.c
> index 5d90b3bc5a25..8862c9ea0d41 100644
> --- a/drivers/gpio/gpio-loongson1.c
> +++ b/drivers/gpio/gpio-loongson1.c
> @@ -1,11 +1,8 @@
> +// SPDX-License-Identifier: GPL-2.0-only
> /*
> * GPIO Driver for Loongson 1 SoC
> *
> - * Copyright (C) 2015-2016 Zhang, Keguang <keguang.zhang@gmail.com>
> - *
> - * This file is licensed under the terms of the GNU General Public
> - * License version 2. This program is licensed "as is" without any
> - * warranty of any kind, whether express or implied.
> + * Copyright (C) 2015-2023 Keguang Zhang <keguang.zhang@gmail.com>
> */
>
> #include <linux/module.h>
> @@ -90,6 +87,6 @@ static struct platform_driver ls1x_gpio_driver = {
>
> module_platform_driver(ls1x_gpio_driver);
>
> -MODULE_AUTHOR("Kelvin Cheung <keguang.zhang@gmail.com>");
Why are you removing credits of the old author?
Bart
> +MODULE_AUTHOR("Keguang Zhang <keguang.zhang@gmail.com>");
> MODULE_DESCRIPTION("Loongson1 GPIO driver");
> MODULE_LICENSE("GPL");
> --
> 2.34.1
>
next prev parent reply other threads:[~2023-03-06 9:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-02 12:52 [PATCH v2 0/5] Devicetree support for Loongson-1 GPIO Keguang Zhang
2023-03-02 12:52 ` [PATCH v2 1/5] gpio: loongson1: Convert to SPDX identifier Keguang Zhang
2023-03-06 9:29 ` Bartosz Golaszewski [this message]
2023-03-07 2:25 ` Keguang Zhang
2023-03-07 13:31 ` Linus Walleij
2023-03-08 2:46 ` Keguang Zhang
2023-03-07 16:48 ` Bartosz Golaszewski
2023-03-08 2:53 ` Keguang Zhang
2023-03-02 12:52 ` [PATCH v2 2/5] gpio: loongson1: Use readl() & writel() Keguang Zhang
2023-03-06 9:30 ` Bartosz Golaszewski
2023-03-07 3:45 ` Keguang Zhang
2023-03-08 9:42 ` David Laight
2023-03-08 11:35 ` Keguang Zhang
2023-03-02 12:52 ` [PATCH v2 3/5] gpio: loongson1: Introduce ls1x_gpio_chip struct Keguang Zhang
2023-03-02 12:52 ` [PATCH v2 4/5] gpio: loongson1: Add DT support Keguang Zhang
2023-03-06 9:39 ` Bartosz Golaszewski
2023-03-07 3:41 ` Keguang Zhang
2023-03-02 12:52 ` [PATCH v2 5/5] dt-bindings: gpio: Add Loongson-1 GPIO Keguang Zhang
2023-03-02 12:58 ` Krzysztof Kozlowski
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='CAMRc=Me=Yrr5BuRaMd4r91URzmdYHWUvVGvLL9YFuZPaV0WYFA@mail.gmail.com' \
--to=brgl@bgdev.pl \
--cc=devicetree@vger.kernel.org \
--cc=keguang.zhang@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@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).