linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lars-Peter Clausen <lars@metafoo.de>
To: Jonathan Cameron <jic23@kernel.org>,
	Shreeya Patel <shreeya.patel23498@gmail.com>
Cc: Himanshu Jha <himanshujha199640@gmail.com>,
	Michael.Hennerich@analog.com, knaack.h@gmx.de, pmeerw@pmeerw.net,
	linux-iio@vger.kernel.org, devel@driverdev.osuosl.org,
	daniel.baluta@nxp.com
Subject: Re: [PATCH 1/3] Staging: iio: adis16209: Use SPDX identifier
Date: Sun, 18 Feb 2018 13:08:47 +0100	[thread overview]
Message-ID: <c81d519c-a0a7-d369-92d6-668e0ace81a6@metafoo.de> (raw)
In-Reply-To: <20180218120243.298bdcdd@archlinux>

On 02/18/2018 01:02 PM, Jonathan Cameron wrote:
> On Sun, 18 Feb 2018 17:07:57 +0530
> Shreeya Patel <shreeya.patel23498@gmail.com> wrote:
> 
>> On Sun, 2018-02-18 at 17:01 +0530, Himanshu Jha wrote:
>>> Hi Shreeya,
>>>   
>> Hi Himanshu,
>>
>>> On Sat, Feb 17, 2018 at 09:34:56PM +0530, Shreeya Patel wrote:  
>>>>
>>>> Use SPDX identifier format instead of GPLv2. Also rearrange the
>>>> headers in alphabetical order.
>>>>
>>>> Signed-off-by: Shreeya Patel <shreeya.patel23498@gmail.com>
>>>> ---
>>>>  drivers/staging/iio/accel/adis16209.c | 7 +++----
>>>>  1 file changed, 3 insertions(+), 4 deletions(-)
>>>>
>>>> diff --git a/drivers/staging/iio/accel/adis16209.c
>>>> b/drivers/staging/iio/accel/adis16209.c
>>>> index 7fcef9a..e3d9f80 100644
>>>> --- a/drivers/staging/iio/accel/adis16209.c
>>>> +++ b/drivers/staging/iio/accel/adis16209.c
>>>> @@ -1,19 +1,18 @@
>>>> +// SPDX-License-Identifier: GPL-2.0+
>>>>  /*
>>>>   * ADIS16209 Dual-Axis Digital Inclinometer and Accelerometer
>>>>   *
>>>>   * Copyright 2010 Analog Devices Inc.
>>>> - *
>>>> - * Licensed under the GPL-2 or later.  
>>> I see that you too are doing similar cleanup which I did a while ago
>>> https://lkml.org/lkml/2018/2/12/255  
>>
>> Yes, Jonathan suggested me to work on adis16209.
>> Your patches were quite useful for me :)
>>
>>> where I got some update suggestions for the patch series. It would be
>>> great if you could update this patch series consistent with the
>>> reviewers.
>>>
>>> For eg: in this patch you changed 
>>>
>>> +// SPDX-License-Identifier: GPL-2.0+
>>>
>>> and therefore
>>>
>>> MODULE_LICENSE("GPL v2");
>>>
>>> should also be changed to 
>>>
>>> MODULE_LICENSE("GPL"); 
>>>
>>> as explained by	Philippe Ombredanne to me in my patch series.  
>>
> I'm not sure that was exactly what Philippe was suggesting.
> He was making the point that the licensing was inconsistent without
> saying which option should be chosen.
> 
> We will need to seek clarification from Analog Devices
> on what their opinion on this is.
> 
> Lars / Michael, any clarification on the right way to resolve this
> inconsistency?

I can't speak for the intended license for code I wasn't involved in.

But I'd in general if there are conflicting licensing information and you
want to be on the safe side choose the more restrictive license. E.g. GPL2+
is compatible with GPL2, but GPL2 is not compatible with GPL2+. So to be
compatible with both choose GPL2.

  reply	other threads:[~2018-02-18 12:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-17 16:02 [PATCH 0/3] adis16209 driver cleanup Shreeya Patel
2018-02-17 16:04 ` [PATCH 1/3] Staging: iio: adis16209: Use SPDX identifier Shreeya Patel
2018-02-18 11:31   ` Himanshu Jha
2018-02-18 11:37     ` Shreeya Patel
2018-02-18 12:02       ` Jonathan Cameron
2018-02-18 12:08         ` Lars-Peter Clausen [this message]
2018-02-18 12:14           ` Lars-Peter Clausen
2018-02-18 12:51             ` Jonathan Cameron
2018-02-18 12:04   ` Jonathan Cameron
2018-02-17 16:07 ` [PATCH 2/3] Staging: iio: adis16209: Remove unnecessary comments and add suitable suffix Shreeya Patel
2018-02-18 12:44   ` Jonathan Cameron
2018-02-17 16:21 ` [PATCH 3/3] Staging: iio: adis16209: Use sign_extend32 and adjust a switch statement Shreeya Patel
2018-02-18 12:47   ` Jonathan Cameron

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=c81d519c-a0a7-d369-92d6-668e0ace81a6@metafoo.de \
    --to=lars@metafoo.de \
    --cc=Michael.Hennerich@analog.com \
    --cc=daniel.baluta@nxp.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=himanshujha199640@gmail.com \
    --cc=jic23@kernel.org \
    --cc=knaack.h@gmx.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=pmeerw@pmeerw.net \
    --cc=shreeya.patel23498@gmail.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;
as well as URLs for NNTP newsgroup(s).