linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: gregory.clement@free-electrons.com (Gregory CLEMENT)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/7] arm64: dts: marvell: use SPDX-License-Identifier for Armada SoCs
Date: Fri, 05 Jan 2018 13:52:38 +0100	[thread overview]
Message-ID: <87vagga2nd.fsf@free-electrons.com> (raw)
In-Reply-To: <20180105134046.12915b36@windsurf.lan> (Thomas Petazzoni's message of "Fri, 5 Jan 2018 13:40:46 +0100")

Hi Thomas,
 
 On ven., janv. 05 2018, Thomas Petazzoni <thomas.petazzoni@free-electrons.com> wrote:

> Hello,
>
> On Fri,  5 Jan 2018 12:53:23 +0100, Gregory CLEMENT wrote:
>> Follow the recent trend for the license description, and also fix the
>> wrongly stated X11 to MIT.
>> 
>> As already pointed on the DT ML, the X11 license text [1] is explicitly
>> for the X Consortium and has a couple of extra clauses. The MIT
>> license text [2] is actually what the current DT files claim.
>> 
>> [1] https://spdx.org/licenses/X11.html
>> [2] https://spdx.org/licenses/MIT.html
>> 
>> Signed-off-by: Gregory CLEMENT <gregory.clement@free-electrons.com>
>> ---
>>  arch/arm64/boot/dts/marvell/armada-371x.dtsi       | 38 +-------------------
>>  arch/arm64/boot/dts/marvell/armada-372x.dtsi       | 38 +-------------------
>>  arch/arm64/boot/dts/marvell/armada-37xx.dtsi       | 38 +-------------------
>>  arch/arm64/boot/dts/marvell/armada-7020.dtsi       | 41 +---------------------
>>  arch/arm64/boot/dts/marvell/armada-7040.dtsi       | 41 +---------------------
>>  arch/arm64/boot/dts/marvell/armada-70x0.dtsi       | 41 +---------------------
>>  arch/arm64/boot/dts/marvell/armada-8020.dtsi       | 41 +---------------------
>>  arch/arm64/boot/dts/marvell/armada-8040.dtsi       | 41 +---------------------
>>  arch/arm64/boot/dts/marvell/armada-8080.dtsi       | 41 +---------------------
>>  arch/arm64/boot/dts/marvell/armada-80x0.dtsi       | 41 +---------------------
>>  arch/arm64/boot/dts/marvell/armada-ap806-dual.dtsi | 41 +---------------------
>>  arch/arm64/boot/dts/marvell/armada-ap806-quad.dtsi | 41 +---------------------
>>  arch/arm64/boot/dts/marvell/armada-ap806.dtsi      | 41 +---------------------
>>  .../dts/marvell/armada-ap810-ap0-octa-core.dtsi    | 41 +---------------------
>>  arch/arm64/boot/dts/marvell/armada-ap810-ap0.dtsi  | 41 +---------------------
>>  arch/arm64/boot/dts/marvell/armada-common.dtsi     |  2 +-
>>  arch/arm64/boot/dts/marvell/armada-cp110.dtsi      |  6 ++--
>>  17 files changed, 18 insertions(+), 596 deletions(-)
>> 
>> diff --git a/arch/arm64/boot/dts/marvell/armada-371x.dtsi b/arch/arm64/boot/dts/marvell/armada-371x.dtsi
>> index 11226f7b9ed9..dc1182ec9fa1 100644
>> --- a/arch/arm64/boot/dts/marvell/armada-371x.dtsi
>> +++ b/arch/arm64/boot/dts/marvell/armada-371x.dtsi
>> @@ -1,3 +1,4 @@
>> +// SPDX-License-Identifier: (GPL-2.0+ OR MIT)
>
> The previous license was GPL-2.0+ or X11, not GPL-2.0+ or MIT. Any
> reason to change from X11 to MIT ?

As explained in the commit log:
" the X11 license text [1] is explicitly for the X Consortium and has a
couple of extra clauses. The MIT license text [2] is actually what the
current DT files claim."

Also as I wrote it was already discussed on the mainling lists (device
tree one and LAKML) see:
http://lists.infradead.org/pipermail/linux-arm-kernel/2017-February/489922.html

Gregory

>
> Thomas
> -- 
> Thomas Petazzoni, CTO, Free Electrons
> Embedded Linux and Kernel engineering
> http://free-electrons.com
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

-- 
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  parent reply	other threads:[~2018-01-05 12:52 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-05 11:53 [PATCH 0/7] use SPDX-License-Identifier for Armada SoCs and boards Gregory CLEMENT
2018-01-05 11:53 ` [PATCH 1/7] arm64: dts: marvell: use SPDX-License-Identifier for Armada SoCs Gregory CLEMENT
2018-01-05 12:40   ` Thomas Petazzoni
2018-01-05 12:45     ` Thomas Petazzoni
2018-01-05 12:52     ` Gregory CLEMENT [this message]
2018-01-05 14:38       ` Andrew Lunn
2018-01-05 14:55         ` Gregory CLEMENT
2018-01-05 15:30           ` Andrew Lunn
2018-01-08 15:27             ` Gregory CLEMENT
2018-01-05 11:53 ` [PATCH 2/7] arm64: dts: marvell: armada-3720-db: use SPDX-License-Identifier Gregory CLEMENT
2018-01-05 11:53 ` [PATCH 3/7] arm64: dts: marvell: armada-3720-espressobin: " Gregory CLEMENT
2018-01-05 11:53 ` [PATCH 4/7] arm64: dts: marvell: armada-7040-db: " Gregory CLEMENT
2018-01-05 11:53 ` [PATCH 5/7] arm64: dts: marvell: armada-8040-db: " Gregory CLEMENT
2018-01-05 11:53 ` [PATCH 6/7] arm64: dts: marvell: armada-8040-mcbin: " Gregory CLEMENT
2018-01-05 11:53 ` [PATCH 7/7] arm64: dts: marvell: armada-8080-db: " Gregory CLEMENT
2018-01-05 11:58 ` [PATCH 0/7] use SPDX-License-Identifier for Armada SoCs and boards Gregory CLEMENT
2018-02-14 12:24 ` Gregory CLEMENT

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=87vagga2nd.fsf@free-electrons.com \
    --to=gregory.clement@free-electrons.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).