linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: "Andreas Färber" <afaerber@suse.de>
Cc: linux-realtek-soc@lists.infradead.org,
	"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE" 
	<linux-arm-kernel@lists.infradead.org>,
	Mark Rutland <mark.rutland@arm.com>,
	devicetree@vger.kernel.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 5/8] arm64: dts: realtek: Change dual-license from MIT to BSD
Date: Fri, 25 Oct 2019 15:52:19 -0500	[thread overview]
Message-ID: <CAL_Jsq+OhiZZ4Ei3wg4s-1z+WsqQSvvRMNrK37Yq+1XR3-3_uA@mail.gmail.com> (raw)
In-Reply-To: <20191020040817.16882-6-afaerber@suse.de>

On Sat, Oct 19, 2019 at 11:08 PM Andreas Färber <afaerber@suse.de> wrote:
>
> Move the SPDX-License-Identifier to the top line and update to SPDX 2.0.
> While at it, switch from GPLv2+/MIT to GPLv2+/BSD2c before adding more.
>
> Suggested-by: Rob Herring <robh@kernel.org>
> Cc: Rob Herring <robh@kernel.org>
> Signed-off-by: Andreas Färber <afaerber@suse.de>
> ---
>  v2: New
>
>  arch/arm64/boot/dts/realtek/rtd1295-zidoo-x9s.dts | 3 +--
>  arch/arm64/boot/dts/realtek/rtd1295.dtsi          | 3 +--
>  arch/arm64/boot/dts/realtek/rtd129x.dtsi          | 3 +--
>  3 files changed, 3 insertions(+), 6 deletions(-)

Acked-by: Rob Herring <robh@kernel.org>

It's really only schema files that I'm pushing towards BSD2C. Maybe in
hindsight we should have done MIT as that's more common in the dts
files.

Rob

  reply	other threads:[~2019-10-25 20:52 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20191020040817.16882-1-afaerber@suse.de>
2019-10-20  4:08 ` [PATCH v2 1/8] dt-bindings: watchdog: realtek: Convert RTD119x to schema Andreas Färber
2019-10-25 21:16   ` Rob Herring
2019-10-25 21:24     ` Andreas Färber
2019-10-27  2:04       ` Andreas Färber
2019-10-20  4:08 ` [PATCH v2 2/8] dt-bindings: rtc: " Andreas Färber
2019-10-25 21:20   ` Rob Herring
2019-10-28 10:46     ` Andreas Färber
2019-10-28 11:29       ` Alexandre Belloni
2019-10-20  4:08 ` [PATCH v2 3/8] dt-bindings: arm: realtek: Tidy up conversion to json-schema Andreas Färber
2019-10-25 21:21   ` Rob Herring
2019-10-26 13:57     ` Andreas Färber
2019-10-20  4:08 ` [PATCH v2 4/8] dt-bindings: arm: realtek: Document RTD1293 and Synology DS418j Andreas Färber
2019-10-29  4:31   ` Andreas Färber
2019-10-20  4:08 ` [PATCH v2 5/8] arm64: dts: realtek: Change dual-license from MIT to BSD Andreas Färber
2019-10-25 20:52   ` Rob Herring [this message]
2019-10-29  4:39     ` Andreas Färber
2019-10-20  4:08 ` [PATCH v2 6/8] arm64: dts: realtek: Add RTD1293 and Synology DS418j Andreas Färber
2019-10-29  4:40   ` Andreas Färber
2019-10-20  4:08 ` [PATCH v2 7/8] dt-bindings: arm: realtek: Document RTD1296 and Synology DS418 Andreas Färber
2019-10-29  4:40   ` Andreas Färber
2019-10-20  4:08 ` [PATCH v2 8/8] arm64: dts: realtek: Add " Andreas Färber
2019-10-29  4:41   ` 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=CAL_Jsq+OhiZZ4Ei3wg4s-1z+WsqQSvvRMNrK37Yq+1XR3-3_uA@mail.gmail.com \
    --to=robh@kernel.org \
    --cc=afaerber@suse.de \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-realtek-soc@lists.infradead.org \
    --cc=mark.rutland@arm.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;
as well as URLs for NNTP newsgroup(s).