[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <71176a0c-dd23-2ca6-7698-9612e4ed6392@suse.de>
Date: Wed, 27 Jun 2018 17:05:14 +0200
From: Andreas Färber <afaerber@...e.de>
To: Daniel Thompson <daniel.thompson@...aro.org>
Cc: Manivannan Sadhasivam <manivannan.sadhasivam@...aro.org>,
robh+dt@...nel.org, liuwei@...ions-semi.com,
96boards@...obotics.com, devicetree@...r.kernel.org,
amit.kucheria@...aro.org, hzhang@...obotics.com,
bdong@...obotics.com, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, manivannanece23@...il.com,
Jeff Chen <jeff.chen@...ions-semi.com>,
"Thomas C. Liau" <thomas.liau@...ions-semi.com>
Subject: Re: [PATCH 1/4] dt-bindings: power: Add Actions Semi S900 SPS
Am 27.06.2018 um 16:57 schrieb Daniel Thompson:
> On Tue, Jun 26, 2018 at 10:11:17PM +0530, Manivannan Sadhasivam wrote:
>>> Question: Should it still be GPL-2.0+ or the new GPL-2.0-or-later?
>>
>> I think GPL-2.0+ is fine.
>
> So... when I saw this I did wonder why one would knowly choose to use a
> deprecated license identifier (https://spdx.org/licenses/ ).
>
> However running `git diff v4.17..v4.18-rc1` through some filters does
> indicate that GPL-2.0+ is the more popular choice by 256 to 0! Doesn't
> mean you couldn't break the mould though ;-).
The kernel.org documentation does not mention the new ones yet.
I checked under LICENSES/ - preferred/GPL-2.0.txt actually lists both
identifiers, and checkpatch.pl did not complain about either.
So for my personal patches I'll be going with the new identifier, unless
I hear of reasons not to.
Cheers,
Andreas
--
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg)
Powered by blists - more mailing lists