From: Chris Brandt <Chris.Brandt@renesas.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Simon Horman <horms@verge.net.au>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: RE: [PATCH 2/2] ARM: dts: r7s9210-rza2mevb: Add support for RZ/A2M EVB
Date: Fri, 30 Nov 2018 16:10:42 +0000 [thread overview]
Message-ID: <OSAPR01MB1553FA10324223CBF4B774DC8AD30@OSAPR01MB1553.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <CAMuHMdU6u8_qhe976afyY6Ydhu3byGZcBP=ipsvNowG3Ci=vGA@mail.gmail.com>
Hi Geert,
On Friday, November 30, 2018 1, Geert wrote:
> > So in our RZ/A BSP that I release to customers I would use this dual
> > license. You can see the exact same license in a number of dts files in
> > mainline.
>
> Note that your file includes
>
> #include <dt-bindings/gpio/gpio.h>
> #include <dt-bindings/pinctrl/r7s9210-pinctrl.h>
>
> both of which are
>
> include/dt-bindings/gpio/gpio.h:/* SPDX-License-Identifier: GPL-2.0 */
> include/dt-bindings/pinctrl/r7s9210-pinctrl.h:/*
> SPDX-License-Identifier: GPL-2.0 */
After I wrote that, I realized that we'll always have:
#include "r7s9210.dtsi"
Which I have as GPL-2.0....so the dual license idea in pointless.
So to make things easy, I'll just drop the dual license thing and just
use SPDX GPL-2.0
Chris
next prev parent reply other threads:[~2018-12-01 3:20 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-29 13:05 [PATCH 0/2] Add Initial Device Tree for RZ/A2 Chris Brandt
2018-11-29 13:05 ` [PATCH 1/2] ARM: dts: r7s9210: Initial SoC device tree Chris Brandt
2018-11-30 11:55 ` Simon Horman
2018-11-30 12:04 ` Chris Brandt
2018-11-30 12:22 ` Simon Horman
2018-11-30 16:03 ` Geert Uytterhoeven
2018-11-30 16:21 ` Chris Brandt
2018-12-04 15:18 ` Geert Uytterhoeven
2018-11-29 13:05 ` [PATCH 2/2] ARM: dts: r7s9210-rza2mevb: Add support for RZ/A2M EVB Chris Brandt
2018-11-30 11:57 ` Simon Horman
2018-11-30 12:20 ` Chris Brandt
2018-11-30 15:59 ` Geert Uytterhoeven
2018-11-30 16:10 ` Chris Brandt [this message]
2018-11-30 16:16 ` Geert Uytterhoeven
2018-12-04 16:01 ` Geert Uytterhoeven
2018-12-04 16:25 ` Chris Brandt
2018-12-04 16:25 ` Chris Brandt
2018-12-04 16:27 ` Geert Uytterhoeven
2018-12-12 2:15 ` Rob Herring
2018-12-12 13:58 ` Chris Brandt
2018-12-12 13:58 ` Chris Brandt
2018-12-12 17:10 ` Rob Herring
2018-12-12 17:10 ` Rob Herring
2018-12-12 18:03 ` Chris Brandt
2018-12-12 18:03 ` Chris Brandt
2018-12-17 15:27 ` Rob Herring
2018-12-17 15:27 ` Rob Herring
2018-12-17 16:22 ` Chris Brandt
2018-12-17 16:22 ` Chris Brandt
2018-12-17 17:00 ` Rob Herring
2018-12-17 17:00 ` Rob Herring
2018-12-17 17:41 ` Chris Brandt
2018-12-17 17:41 ` Chris Brandt
2018-12-18 7:42 ` Geert Uytterhoeven
2018-12-18 7:42 ` Geert Uytterhoeven
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=OSAPR01MB1553FA10324223CBF4B774DC8AD30@OSAPR01MB1553.jpnprd01.prod.outlook.com \
--to=chris.brandt@renesas.com \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=horms@verge.net.au \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.