From: Alex Elder <elder@riscstar.com>
To: Emil Renner Berthing <emil.renner.berthing@canonical.com>,
Conor Dooley <conor@kernel.org>
Cc: Krzysztof Kozlowski <krzk@kernel.org>,
Guodong Xu <guodong@riscstar.com>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Emil Renner Berthing <kernel@esmil.dk>,
rafal@milecki.pl, Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Neil Armstrong <neil.armstrong@linaro.org>,
Heiko Stuebner <heiko.stuebner@cherry.de>,
Michael Zhu <michael.zhu@starfivetech.com>,
Drew Fustini <drew@beagleboard.org>,
Alexandru Stan <ams@frame.work>, Daniel Schaefer <dhs@frame.work>,
Sandie Cao <sandie.cao@deepcomputing.io>,
Yuning Liang <yuning.liang@deepcomputing.io>,
Huiming Qiu <huiming.qiu@deepcomputing.io>,
linux@frame.work, devicetree@vger.kernel.org,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 3/3] riscv: dts: starfive: add DeepComputing FML13V01 board device tree
Date: Wed, 23 Oct 2024 12:20:44 -0500 [thread overview]
Message-ID: <01a7b872-494f-4ea1-aef5-b40abc4bec06@riscstar.com> (raw)
In-Reply-To: <CAJM55Z_jp7ZGUcV=4Ciq0ZMPbrf_YARpSDwWgxBa9OjbYzhiFw@mail.gmail.com>
On 10/23/24 11:49 AM, Emil Renner Berthing wrote:
>> Ultimately, it is up to Emil how he wants these laid out.
> Thanks, but I agree. Please begin with a patch moving the nodes that are no
> longer common out of jh7110-common.dtsi and into the vf2, mars and pine64
> consumers. You should probably do the same with the &usb0 node instead
> of overriding the dr_mode property.
>
> /Emil
Thenk you Emil, we will prepare the next version of the series
to do these things.
-Alex
prev parent reply other threads:[~2024-10-23 17:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-20 13:49 [PATCH v5 0/3] Add DeepComputing FML13V01 board dts Guodong Xu
2024-10-20 13:49 ` [PATCH v5 1/3] dt-bindings: vendor: add deepcomputing Guodong Xu
2024-10-20 13:49 ` [PATCH v5 2/3] dt-bindings: riscv: starfive: add deepcomputing,fml13v01 Guodong Xu
2024-10-23 16:38 ` Emil Renner Berthing
2024-10-20 13:49 ` [PATCH v5 3/3] riscv: dts: starfive: add DeepComputing FML13V01 board device tree Guodong Xu
2024-10-21 7:17 ` Krzysztof Kozlowski
2024-10-21 11:16 ` Conor Dooley
2024-10-21 12:47 ` Krzysztof Kozlowski
2024-10-21 13:44 ` Alex Elder
2024-10-21 16:48 ` Conor Dooley
2024-10-23 16:49 ` Emil Renner Berthing
2024-10-23 17:20 ` Alex Elder [this message]
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=01a7b872-494f-4ea1-aef5-b40abc4bec06@riscstar.com \
--to=elder@riscstar.com \
--cc=ams@frame.work \
--cc=aou@eecs.berkeley.edu \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dhs@frame.work \
--cc=drew@beagleboard.org \
--cc=emil.renner.berthing@canonical.com \
--cc=gregkh@linuxfoundation.org \
--cc=guodong@riscstar.com \
--cc=heiko.stuebner@cherry.de \
--cc=huiming.qiu@deepcomputing.io \
--cc=kernel@esmil.dk \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux@frame.work \
--cc=michael.zhu@starfivetech.com \
--cc=neil.armstrong@linaro.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=rafal@milecki.pl \
--cc=robh@kernel.org \
--cc=sandie.cao@deepcomputing.io \
--cc=yuning.liang@deepcomputing.io \
/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