linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Matthias Schiffer <matthias.schiffer@ew.tq-group.com>
Cc: Shawn Guo <shawnguo@kernel.org>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Fabio Estevam <festevam@gmail.com>,
	NXP Linux Team <linux-imx@nxp.com>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	Markus Niebel <Markus.Niebel@ew.tq-group.com>
Subject: Re: [PATCH 3/3] ARM: dts: imx6qdl: add TQ-Systems MBa6x device trees
Date: Tue, 26 Oct 2021 15:15:12 -0500	[thread overview]
Message-ID: <YXhh0B3xX3Gx6vTM@robh.at.kernel.org> (raw)
In-Reply-To: <20211013111202.6231-3-matthias.schiffer@ew.tq-group.com>

On Wed, Oct 13, 2021 at 01:12:02PM +0200, Matthias Schiffer wrote:
> From: Markus Niebel <Markus.Niebel@ew.tq-group.com>
> 
> Add device trees for the MBa6x mainboard with TQMa6Q/QP/DL SoMs.
> 
> Files are imported with (GPL-2.0-or-later OR MIT) license where the
> copyright is held fully by TQ-Systems. Other files with less clear
> copyright ownership use their original GPL-2.0-or-later license.

Thanks for giving it some thought, but I don't think 'or-later' works 
given imx6dl.dtsi is GPL-2.0-only. It's kind of a mess though:

$ git grep -ho 'SPDX.*' arch/arm/boot/dts/imx6dl* | sort -u
SPDX-License-Identifier: GPL-2.0
SPDX-License-Identifier: GPL-2.0+
SPDX-License-Identifier: GPL-2.0-only
SPDX-License-Identifier: GPL-2.0-only */
SPDX-License-Identifier: GPL-2.0-or-later
SPDX-License-Identifier: GPL-2.0-or-later OR MIT
SPDX-License-Identifier: (GPL-2.0 or MIT)
SPDX-License-Identifier: GPL-2.0 or MIT
SPDX-License-Identifier: (GPL-2.0 OR MIT)
SPDX-License-Identifier: GPL-2.0 OR MIT
SPDX-License-Identifier: (GPL-2.0+ OR MIT)
SPDX-License-Identifier: GPL-2.0+ OR MIT
SPDX-License-Identifier: GPL-2.0 OR X11

The dts files are all too intertwined to be different licenses IMO.

Rob

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2021-10-26 20:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-13 11:12 [PATCH 1/3] dt-bindings: arm: fsl: add TQ-Systems boards based on i.MX6Q/QP/DL Matthias Schiffer
2021-10-13 11:12 ` [PATCH 2/3] ARM: dts: imx6qdl: tqma6: add ERR006687 hardware workaround for "a" variant Matthias Schiffer
2021-10-13 11:12 ` [PATCH 3/3] ARM: dts: imx6qdl: add TQ-Systems MBa6x device trees Matthias Schiffer
2021-10-26 20:15   ` Rob Herring [this message]
2021-10-26 20:16 ` [PATCH 1/3] dt-bindings: arm: fsl: add TQ-Systems boards based on i.MX6Q/QP/DL Rob Herring

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=YXhh0B3xX3Gx6vTM@robh.at.kernel.org \
    --to=robh@kernel.org \
    --cc=Markus.Niebel@ew.tq-group.com \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthias.schiffer@ew.tq-group.com \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@kernel.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).