From: "Andreas Färber" <afaerber@suse.de>
To: Daniel Thompson <daniel.thompson@linaro.org>
Cc: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
robh+dt@kernel.org, liuwei@actions-semi.com,
96boards@ucrobotics.com, devicetree@vger.kernel.org,
amit.kucheria@linaro.org, hzhang@ucrobotics.com,
bdong@ucrobotics.com, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, manivannanece23@gmail.com,
Jeff Chen <jeff.chen@actions-semi.com>,
"Thomas C. Liau" <thomas.liau@actions-semi.com>
Subject: Re: [PATCH 1/4] dt-bindings: power: Add Actions Semi S900 SPS
Date: Wed, 27 Jun 2018 17:05:14 +0200 [thread overview]
Message-ID: <71176a0c-dd23-2ca6-7698-9612e4ed6392@suse.de> (raw)
In-Reply-To: <20180627145713.uao2gr5kknk2cypk@holly.lan>
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)
next prev parent reply other threads:[~2018-06-27 15:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-11 16:40 [PATCH 0/4] Add Actions Semi S900 SPS support Manivannan Sadhasivam
2018-04-11 16:40 ` [PATCH 1/4] dt-bindings: power: Add Actions Semi S900 SPS Manivannan Sadhasivam
2018-04-16 18:48 ` Rob Herring
2018-06-24 13:04 ` Andreas Färber
2018-06-26 16:41 ` Manivannan Sadhasivam
2018-06-27 14:57 ` Daniel Thompson
2018-06-27 15:05 ` Andreas Färber [this message]
2018-06-27 15:10 ` Manivannan Sadhasivam
2018-04-11 16:40 ` [PATCH 2/4] arm64: dts: actions: Add S900 SPS node Manivannan Sadhasivam
2018-06-24 13:06 ` Andreas Färber
2018-04-11 16:40 ` [PATCH 3/4] soc: actions: sps: Add S900 power domains Manivannan Sadhasivam
2018-06-24 13:07 ` Andreas Färber
2018-09-30 15:46 ` Andreas Färber
2018-04-11 16:40 ` [PATCH 4/4] soc: actions: Fix help text in Kconfig for OWL_PM_DOMAINS Manivannan Sadhasivam
2018-06-24 13:28 ` Andreas Färber
2018-06-24 14:01 ` [PATCH] soc: actions: Update SPS help text for S700 Andreas Färber
2018-09-22 20:11 ` Andreas Färber
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=71176a0c-dd23-2ca6-7698-9612e4ed6392@suse.de \
--to=afaerber@suse.de \
--cc=96boards@ucrobotics.com \
--cc=amit.kucheria@linaro.org \
--cc=bdong@ucrobotics.com \
--cc=daniel.thompson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=hzhang@ucrobotics.com \
--cc=jeff.chen@actions-semi.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liuwei@actions-semi.com \
--cc=manivannan.sadhasivam@linaro.org \
--cc=manivannanece23@gmail.com \
--cc=robh+dt@kernel.org \
--cc=thomas.liau@actions-semi.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
all inboxes | Powered by JetHome®