From: patchwork-bot+linux-riscv@kernel.org
To: Andrei Lalaev <andrey.lalaev@gmail.com>
Cc: linux-riscv@lists.infradead.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org, chen.wang@linux.dev,
inochiama@gmail.com, pjw@kernel.org, palmer@dabbelt.com,
aou@eecs.berkeley.edu, alex@ghiti.fr, me@ziyao.cc,
devicetree@vger.kernel.org, sophgo@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] Do not reserve memory for coprocessor FW
Date: Sun, 01 Nov 2026 22:16:14 +0000 [thread overview]
Message-ID: <179357137404.2624073.6489638020939885844.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260921-sophgo-remove-coprocessor-node-v1-0-ace29446b327@gmail.com>
Hello:
This series was applied to riscv/linux.git (fixes)
by Inochi Amaoto <inochiama@gmail.com>:
On Mon, 21 Sep 2026 17:08:58 +0200 you wrote:
> Milk-V Duo and Duo-256M reserve a region for coprocessor FW at
> the end of RAM. It is not correct because:
> - FSBL can be configured to load FW into a different region
> - if no firmware is loaded, the reserved memory is wasted
>
> As explained in [1, 2], FSBL should reserve the region at runtime.
>
> [...]
Here is the summary with links:
- [1/2] riscv: dts: sophgo: cv1800b-milkv-duo: drop reserved memory node
https://git.kernel.org/riscv/c/6645398c4621
- [2/2] riscv: dts: sophgo: sg2002-milkv-duo256m: drop reserved memory node
https://git.kernel.org/riscv/c/60e4cafd3090
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-11-01 22:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-21 15:08 Andrei Lalaev
2026-09-21 15:08 ` [PATCH 1/2] riscv: dts: sophgo: cv1800b-milkv-duo: drop reserved memory node Andrei Lalaev
2026-09-21 15:09 ` [PATCH 2/2] riscv: dts: sophgo: sg2002-milkv-duo256m: " Andrei Lalaev
2026-10-09 9:47 ` [PATCH 0/2] Do not reserve memory for coprocessor FW Inochi Amaoto
2026-11-01 22:16 ` patchwork-bot+linux-riscv [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=179357137404.2624073.6489638020939885844.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=alex@ghiti.fr \
--cc=andrey.lalaev@gmail.com \
--cc=aou@eecs.berkeley.edu \
--cc=chen.wang@linux.dev \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=inochiama@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=me@ziyao.cc \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=robh@kernel.org \
--cc=sophgo@lists.linux.dev \
/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
all inboxes | Powered by JetHome®