linux-spi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Philippe Ombredanne <pombredanne@nexb.com>
Cc: Andi Shyti <andi@etezian.org>,
	Andi Shyti <andi.shyti@samsung.com>,
	Kukjin Kim <kgene@kernel.org>, Mark Brown <broonie@kernel.org>,
	linux-spi@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
	LKML <linux-kernel@vger.kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] spi: s3c64xx: add SPDX identifier
Date: Tue, 12 Dec 2017 16:35:53 +0100	[thread overview]
Message-ID: <CAJKOXPeCBPdCi2NnpBWimb4Py_zDZrsSK9o1cCswKM+XNeyqxQ@mail.gmail.com> (raw)
In-Reply-To: <CAOFm3uEAzEgN-PgSOccbwO3aWfABsHywUmm8eXasR8CXy=NPJQ@mail.gmail.com>

On Tue, Dec 12, 2017 at 4:24 PM, Philippe Ombredanne
<pombredanne@nexb.com> wrote:
> Dear Krzysztof,
>
> On Tue, Dec 12, 2017 at 4:00 PM, Krzysztof Kozlowski <krzk@kernel.org> wrote:
>> On Tue, Dec 12, 2017 at 3:48 PM, Philippe Ombredanne
>> <pombredanne@nexb.com> wrote:
>>> On Tue, Dec 12, 2017 at 2:45 PM, Krzysztof Kozlowski <krzk@kernel.org> wrote:
>>>> On Tue, Dec 12, 2017 at 2:03 PM, Andi Shyti <andi@etezian.org> wrote:
>>>>> Hi Krzysztof,
>>>>>
>>>>>> > - * Copyright (C) 2009 Samsung Electronics Ltd.
>>>>>> > - *     Jaswinder Singh <jassi.brar@samsung.com>
>>>>>> > - *
>>>>>> > - * This program is free software; you can redistribute it and/or modify
>>>>>> > - * it under the terms of the GNU General Public License as published by
>>>>>> > - * the Free Software Foundation; either version 2 of the License, or
>>>>>> > - * (at your option) any later version.
>>>>>> > - *
>>>>>> > - * This program is distributed in the hope that it will be useful,
>>>>>> > - * but WITHOUT ANY WARRANTY; without even the implied warranty of
>>>>>> > - * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
>>>>>> > - * GNU General Public License for more details.
>>>>>> > - */
>>>>>> > +// SPDX-License-Identifier: GPL-2.0
>>>>>>
>>>>>
>>>>>> Existing license corresponds to GPL-2.0+, not GPL-2.0.
>>>>>
>>>>> mmmhhh... isn't it deprecated from 2.0rc2? Current SPDX version
>>>>> 2.6 doesn't have GPL-2.0+ in the list of licenses.
>>>>>
>>>>> https://spdx.org/licenses/
>>>>>
>>>>> I can improve the commit log to state it more clearly. Would that
>>>>> work?
>>>>
>>>> No. The license identifier is deprecated, not the license itself.
>>>> Instead the, the SPDX says: <<This new syntax supports the ability to
>>>> use a simple “+” operator after a license short identifier to indicate
>>>> “or later version” (e.g. GPL-2.0+)>>. The spec [1] mentions it again:
>>>> "An SPDX License List Short Form Identifier with a unary"+" operator
>>>> suffix to represent the current version of the license or any later
>>>> version.  For example: GPL-2.0+"
>>>>
>>>> Existing kernel sources follow this convention.
>>>>
>>>>> BTW, is it really a change of license?
>>>>
>>>> Yes, it is. Or maybe not license itself but it terms and specific
>>>> elements. GPL-2.0 does not say "any later option at your choice". Let
>>>> me quote:
>>>> "Each version is given a distinguishing version number. If the Program
>>>> specifies a version number of this License which applies to it and
>>>> "any later version", you have the option of following the terms and
>>>> conditions either of that version or of any later version published by
>>>> the Free Software Foundation. If the Program does not specify a
>>>> version number of this License, you may choose any version ever
>>>> published by the Free Software Foundation." [2]
>>>>
>>>> What to add more here? GPL-2.0 only does not allow you to use any
>>>> later version ever published by FSF.
>>>>
>>>>>
>>>>>> Why changing the comment style?
>>>>>
>>>>> That's SPDX, right? by adding the SPDX-License-Identifier the
>>>>> GPLv2 statement becomes redundant and we can remove some lines.
>>>>
>>>> But it does not explain why existing comment has to be rewritten into //.
>>>>
>>>> [1] https://spdx.org/spdx-specification-21-web-version
>>>> [2] https://www.gnu.org/licenses/old-licenses/gpl-2.0.en.html
>>>>
>>>> Best regards,
>>>> Krzysztof
>>>
>>> IMHO you should refer to Thomas doc patches instead of looking for
>>> details elsewhere [1]
>>> They are the authoritative doc for the kernel.
>>
>> I was actually checking this with existing source code (after applying
>> these patches) and GPLv2.0+any_later was converted to "GPL-2.0+".
>> Let's look at specific example:
>> https://lkml.org/lkml/2017/12/4/946
>> "+ For 'GNU General Public License (GPL) version 2 or any later version' use:
>> +    SPDX-License-Identifier: GPL-2.0+"
>>
>> I do not understand then whether you are agreeing or arguing with my point. :)
>>
>> Best regards,
>> Krzysztof
>>
>>>
>>> CC: Greg Kroah-Hartman
>>> CC: Thomas Gleixner
>>>
>>> [1] https://lkml.org/lkml/2017/12/4/934
>
> Here, this should be as a top line:
>
> // SPDX-License-Identifier: GPL-2.0+
>
>
> So I agree with the SPDX id but also pointing to the use of the C++ //
> comment style as requested by Linus [1]

Thanks for the reference. I see that Linus prefers converting entire
comment into // style. I was not arguing about SPDX line but entire
existing copyright comment which follows it:

> +//
> +// Copyright (c) 2009 Samsung Electronics Co., Ltd.
> +//      Jaswinder Singh <jassi.brar@samsung.com>

Best regards,
Krzysztof

>
> [1] https://lkml.org/lkml/2017/11/25/133
> [2] https://lkml.org/lkml/2017/11/25/125
> [3] https://lkml.org/lkml/2017/11/2/715
> [4] https://lkml.org/lkml/2017/11/2/805
>
> --
> Cordially
> Philippe Ombredanne

  reply	other threads:[~2017-12-12 15:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20171212075830epcas2p31afc4a2e715e857694082748fd2bbe49@epcas2p3.samsung.com>
2017-12-12  7:58 ` [PATCH] spi: s3c64xx: add SPDX identifier Andi Shyti
2017-12-12  9:17   ` Krzysztof Kozlowski
2017-12-12 10:07     ` Mark Brown
2017-12-12 10:13       ` Krzysztof Kozlowski
2017-12-12 10:31         ` Mark Brown
     [not found]     ` <CAJKOXPfdKyT8-bpM7tmveb3jWCRSSXwnkifhsRw_ag8X9z0W8A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-12-12 13:03       ` Andi Shyti
2017-12-12 13:45         ` Krzysztof Kozlowski
     [not found]           ` <CAJKOXPc8o2_bMbXjwPopOtsoML0NqOzzHnYXCL9oU9VkU2cQYA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-12-12 14:48             ` Philippe Ombredanne
2017-12-12 15:00               ` Krzysztof Kozlowski
2017-12-12 15:24                 ` Philippe Ombredanne
2017-12-12 15:35                   ` Krzysztof Kozlowski [this message]
2017-12-13  1:48                     ` Andi Shyti
2017-12-13  7:23                       ` Krzysztof Kozlowski
     [not found]                       ` <20171213014854.GG20051-8vUhnHFVuGn35fTxX1Dczw@public.gmane.org>
2017-12-13  9:38                         ` Mark Brown

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=CAJKOXPeCBPdCi2NnpBWimb4Py_zDZrsSK9o1cCswKM+XNeyqxQ@mail.gmail.com \
    --to=krzk@kernel.org \
    --cc=andi.shyti@samsung.com \
    --cc=andi@etezian.org \
    --cc=broonie@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=kgene@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=pombredanne@nexb.com \
    --cc=tglx@linutronix.de \
    /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).