From: Jonathan Cameron <jic23@kernel.org>
To: Amir Mahdi Ghorbanian <indigoomega021@gmail.com>
Cc: lars@metafoo.de, Michael.Hennerich@analog.com, knaack.h@gmx.de,
pmeerw@pmeerw.net, gregkh@linuxfoundation.org,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
Barry Song <21cnbao@gmail.com>
Subject: Re: [PATCH] Staging: iio: adis16240: fixed a SPDX identifier tag mistake
Date: Sat, 22 Dec 2018 17:38:07 +0000 [thread overview]
Message-ID: <20181222173807.0284c33a@archlinux> (raw)
In-Reply-To: <1545253651-13891-1-git-send-email-indigoomega021@gmail.com>
On Wed, 19 Dec 2018 13:07:31 -0800
Amir Mahdi Ghorbanian <indigoomega021@gmail.com> wrote:
> Fixed a coding style mistake by adding the SPDX identifier tag to the
> first line of the code.
>
> Signed-off-by: Amir Mahdi Ghorbanian <indigoomega021@gmail.com>
*groans* Another one where the MODULE_LICENSE is different.
Michael, Analog copyright, so if you want to express a view on
the intent that would be great.
My feeling would be that the MODULE_LICENSE is the wrong one given it's
easier to get that wrong than to add an 'or later' to the text..
On these I generally want an ack from the copyright holder anyway
just to be sure everything is in order.
Thanks,
Jonathan
> ---
> drivers/staging/iio/accel/adis16240.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/staging/iio/accel/adis16240.c b/drivers/staging/iio/accel/adis16240.c
> index 24e525f..2c40189 100644
> --- a/drivers/staging/iio/accel/adis16240.c
> +++ b/drivers/staging/iio/accel/adis16240.c
> @@ -1,9 +1,9 @@
> +// SPDX-License-Identifier: GPL-2.0+
> /*
> * ADIS16240 Programmable Impact Sensor and Recorder driver
> *
> * Copyright 2010 Analog Devices Inc.
> *
> - * Licensed under the GPL-2 or later.
> */
>
> #include <linux/interrupt.h>
prev parent reply other threads:[~2018-12-22 17:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-19 21:07 [PATCH] Staging: iio: adis16240: fixed a SPDX identifier tag mistake Amir Mahdi Ghorbanian
2018-12-22 17:38 ` Jonathan Cameron [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=20181222173807.0284c33a@archlinux \
--to=jic23@kernel.org \
--cc=21cnbao@gmail.com \
--cc=Michael.Hennerich@analog.com \
--cc=gregkh@linuxfoundation.org \
--cc=indigoomega021@gmail.com \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
/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