linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: zajec5@gmail.com (Rafał Miłecki)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: BCM53573: Relicense SoC file to the GPL 2.0+ / MIT
Date: Thu, 20 Sep 2018 13:39:28 +0200	[thread overview]
Message-ID: <20180920113928.27048-1-zajec5@gmail.com> (raw)

From: Rafa? Mi?ecki <rafal@milecki.pl>

This matches licensing used by most of BCM5301X files and is preferred as:
1) GPL 2.0+ makes it clearly compatible with Linux kernel
2) MIT is also permissive but preferred over ISC

This file has been developed by me & once modified by Rob dropping a
single leading zero in an UART address.

Signed-off-by: Rafa? Mi?ecki <rafal@milecki.pl>
---
Rob: you modified this file by commit 8dccafaa281a ("arm: dts: fix
unit-address leading 0s") with a trivial change generated by a simple
perl command.

I'm not sure if I even need your Ack, but I'm not a lawyer after all.
Maybe you could ack this patch, just to keep it 100% legally clear?
---
 arch/arm/boot/dts/bcm53573.dtsi | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/arch/arm/boot/dts/bcm53573.dtsi b/arch/arm/boot/dts/bcm53573.dtsi
index 453a2a37dabd..5054fa9eb0d0 100644
--- a/arch/arm/boot/dts/bcm53573.dtsi
+++ b/arch/arm/boot/dts/bcm53573.dtsi
@@ -1,7 +1,6 @@
+// SPDX-License-Identifier: GPL-2.0-or-later OR MIT
 /*
  * Copyright (C) 2016 Rafa? Mi?ecki <rafal@milecki.pl>
- *
- * Licensed under the ISC license.
  */
 
 #include <dt-bindings/gpio/gpio.h>
-- 
2.13.7

             reply	other threads:[~2018-09-20 11:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-20 11:39 Rafał Miłecki [this message]
2018-10-11 11:13 ` [PATCH] ARM: dts: BCM53573: Relicense SoC file to the GPL 2.0+ / MIT Rob Herring
2018-10-11 18:17 ` Florian Fainelli

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=20180920113928.27048-1-zajec5@gmail.com \
    --to=zajec5@gmail.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).