From: Jisheng Zhang <jszhang@kernel.org>
To: Drew Fustini <dfustini@baylibre.com>
Cc: Conor Dooley <conor@kernel.org>, Guo Ren <guoren@kernel.org>,
Fu Wei <wefu@redhat.com>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
linux-riscv@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Robert Nelson <robertcnelson@beagleboard.org>,
Jason Kridner <jkridner@beagleboard.org>
Subject: Re: [PATCH 1/3] riscv: dts: thead: add BeagleV Ahead board device tree
Date: Mon, 24 Jul 2023 08:23:22 +0800 [thread overview]
Message-ID: <ZL3Eenj4lGZDhZTM@xhacker> (raw)
In-Reply-To: <ZL1jlacHj7sgNg8M@x1>
On Sun, Jul 23, 2023 at 10:29:57AM -0700, Drew Fustini wrote:
> On Sun, Jul 23, 2023 at 11:32:17AM +0100, Conor Dooley wrote:
> > On Sat, Jul 22, 2023 at 02:55:39PM -0700, Drew Fustini wrote:
> >
> > > +++ b/arch/riscv/boot/dts/thead/th1520-beaglev-ahead.dts
> > > @@ -0,0 +1,61 @@
> > > +// SPDX-License-Identifier: GPL-2.0
> >
> > Hmm, should this not be dual licensed?
> > I notice the other th1520 stuff isn't either..
>
> Good point, I'll resubmit with a dual license.
>
> Jisheng: are you okay with the other arch/riscv/boot/dts/thead files
> changing to a dual license?
When cooking the initial patch, I wrote the lpi4a dts files from
scratch based on sipeed opened sch file, and currently only I made
contributions to them, so it's easy to make the lpi4a dts files
dual license.
However, when constructing the th1520.dtsi, I refered the T-HEAD's
opensourced yocto repo(in fact, that's the only sourcecode/doc I have
at that time), and the license there is GPL-2.0. That's
also the reason why copyright of Alibaba Group Holding Limited is
added to th1520.dtsi. I'm not sure how to make th1520.dtsi dual
license. At least, this needs help from Guo Ren. Any suggestion is
appreciated.
>
> >
> >
> > > + memory@0 {
> > > + device_type = "memory";
> > > + reg = <0x0 0x00000000 0x1 0x00000000>;
> >
> > There's some extra spaces in here for some reason.
>
> Thanks for spotting that. I'll fix when I resubmit with dual licnese.
>
> Drew
next prev parent reply other threads:[~2023-07-24 0:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-22 21:55 [PATCH 0/3] riscv: Add BeagleV Ahead board support Drew Fustini
2023-07-22 21:55 ` [PATCH 1/3] riscv: dts: thead: add BeagleV Ahead board device tree Drew Fustini
2023-07-22 23:04 ` Guo Ren
2023-07-23 10:32 ` Conor Dooley
2023-07-23 17:29 ` Drew Fustini
2023-07-24 0:23 ` Jisheng Zhang [this message]
2023-07-24 10:37 ` Conor Dooley
2023-07-24 12:07 ` Guo Ren
2023-07-27 9:55 ` Kwanghoon Son
2023-07-27 16:07 ` Jisheng Zhang
2023-07-27 23:59 ` Drew Fustini
2023-07-22 21:55 ` [PATCH 2/3] dt-bindings: riscv: Add BeagleV Ahead board compatibles Drew Fustini
2023-07-22 23:02 ` Guo Ren
2023-07-23 6:36 ` Krzysztof Kozlowski
2023-07-22 21:55 ` [PATCH 3/3] MAINTAINERS: add reviewer for T-Head RISC-V SoC support Drew Fustini
2023-07-22 23:01 ` Guo Ren
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=ZL3Eenj4lGZDhZTM@xhacker \
--to=jszhang@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dfustini@baylibre.com \
--cc=guoren@kernel.org \
--cc=jkridner@beagleboard.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robertcnelson@beagleboard.org \
--cc=robh+dt@kernel.org \
--cc=wefu@redhat.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