All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Brandt <Chris.Brandt@renesas.com>
To: Simon Horman <horms@verge.net.au>
Cc: Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-renesas-soc@vger.kernel.org"
	<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 12:20:37 +0000	[thread overview]
Message-ID: <OSAPR01MB155353707920BFFEB7C4280E8AD30@OSAPR01MB1553.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <20181130115713.blmkvpa2vsdnqdt6@verge.net.au>

Hi Simon,

On Friday, November 30, 2018, Simon Horman wrote:
> > +  - RZ/A2M Eval Board (RTK7921053S00000BE)
> > +    compatible = "renesas,rza2mevb", "renesas,r7s9210"
> >    - RZN1D-DB (RZ/N1D Demo Board for the RZ/N1D 400 pins package)
> >      compatible = "renesas,rzn1d400-db", "renesas,r9a06g032"
> >    - Salvator-X (RTP0RC7795SIPB0010S)
> 
> Pleas separate the change above into a separate patch.
> Such changes typically go upstream via a separate branch.

OK. Looking through the history log, I saw it different ways, so I was 
not sure.


> I am wondering about the motivation for dual-licensing this file.
> It does not seem to be something Renesas has done before with
> upstream DT.
> 
> I am also wondering if the dual licence, if it remains, can be
> described using SPDX.

A while back, I was reading/hearing about how board DT file do not have 
to be GPL and the user should not have to be forced to make this GPL. 
(Maybe at some ELC conference or on LWN or something)
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.

Since there is no SPDX for this, I figure Rob might have some opinion on
the matter.
And, if I have to make it GLP for the mainline version, then I will just
replace the license when I release the customer BSP (since I wrote it, 
I can do that). But, I would be nice to keep the BSP version as close to
mainline as I can.

Chris

  reply	other threads:[~2018-11-30 23:29 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 [this message]
2018-11-30 15:59       ` Geert Uytterhoeven
2018-11-30 16:10         ` Chris Brandt
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=OSAPR01MB155353707920BFFEB7C4280E8AD30@OSAPR01MB1553.jpnprd01.prod.outlook.com \
    --to=chris.brandt@renesas.com \
    --cc=devicetree@vger.kernel.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.