public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Leo Liang <ycliang@andestech.com>
To: E Shattow <e@freeshell.de>
Cc: Rick Chen <rick@andestech.com>,
	Minda Chen <minda.chen@starfivetech.com>,
	 Hal Feng <hal.feng@starfivetech.com>,
	Tom Rini <trini@konsulko.com>, <u-boot@lists.denx.de>,
	Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
Subject: Re: [PATCH v3 2/4] riscv: dts: starfive: sync visionfive2 overrides with upstream Linux for-next
Date: Fri, 19 Sep 2025 18:58:23 +0800	[thread overview]
Message-ID: <aM03T06p-8iSTbA_@swlinux02> (raw)
In-Reply-To: <20250917000254.1134031-3-e@freeshell.de>

On Tue, Sep 16, 2025 at 05:02:23PM -0700, E Shattow wrote:
> Sync automatic dtsi inclusion overrides for JH7110 CPU with upstream
> "riscv: dts: starfive: jh7110: bootph-pre-ram hinting needed by boot
> loader" from upstream Linux conor/riscv-dt-for-next commit 8181cc2f3f21
> 
> Signed-off-by: E Shattow <e@freeshell.de>
> ---
>  arch/riscv/dts/jh7110-u-boot.dtsi | 81 ++++++++++++-------------------
>  1 file changed, 31 insertions(+), 50 deletions(-)

Reviewed-by: Leo Yu-Chi Liang <ycliang@andestech.com>

  parent reply	other threads:[~2025-09-19 10:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-17  0:02 [PATCH v3 0/4] riscv: dts: starfive: prune redundant jh7110-common E Shattow
2025-09-17  0:02 ` [PATCH v3 1/4] riscv: dts: starfive: prune redundant jh7110-common overrides E Shattow
2025-09-19 10:51   ` Leo Liang
2025-09-17  0:02 ` [PATCH v3 2/4] riscv: dts: starfive: sync visionfive2 overrides with upstream Linux for-next E Shattow
2025-09-17  2:59   ` E Shattow
2025-09-19 10:58   ` Leo Liang [this message]
2025-09-17  0:02 ` [PATCH v3 3/4] riscv: dts: starfive: visionfive2 depend on SYS_CPU automatic dtsi inclusion E Shattow
2025-09-19 10:58   ` Leo Liang
2025-09-17  0:02 ` [PATCH v3 4/4] configs: starfive: Use visionfive2 DEVICE_TREE_INCLUDES dtsi named similar to defconfig E Shattow
2025-09-19 10:59   ` Leo Liang

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=aM03T06p-8iSTbA_@swlinux02 \
    --to=ycliang@andestech.com \
    --cc=e@freeshell.de \
    --cc=hal.feng@starfivetech.com \
    --cc=heinrich.schuchardt@canonical.com \
    --cc=minda.chen@starfivetech.com \
    --cc=rick@andestech.com \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    /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