From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Anton Johansson <anjo@rev.ng>, qemu-devel@nongnu.org
Cc: pierrick.bouvier@linaro.org, alistair.francis@wdc.com,
richard.henderson@linaro.org, palmer@dabbelt.com
Subject: Re: [PATCH v2 0/3] single-binary: Prepare hw/riscv for single compilation
Date: Tue, 28 Oct 2025 08:25:43 +0100 [thread overview]
Message-ID: <494cb717-88eb-4243-a39c-62e94f89f285@linaro.org> (raw)
In-Reply-To: <20251027-feature-single-binary-hw-v1-v2-0-44478d589ae9@rev.ng>
On 27/10/25 13:35, Anton Johansson wrote:
> Anton Johansson (3):
> hw/riscv: Use generic hwaddr for firmware addressses
> hw/riscv: Widen OpenSBI dynamic info struct
Queuing patches #1 (without kernel hwaddr change) and #3, thanks!
next prev parent reply other threads:[~2025-10-28 7:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-27 12:35 [PATCH v2 0/3] single-binary: Prepare hw/riscv for single compilation Anton Johansson via
2025-10-27 12:35 ` [PATCH v2 1/3] hw/riscv: Use generic hwaddr for firmware addressses Anton Johansson via
2025-10-27 12:39 ` Philippe Mathieu-Daudé
2025-10-27 18:13 ` Anton Johansson via
2025-10-27 12:35 ` [PATCH v2 2/3] hw/riscv: Replace target_ulong uses Anton Johansson via
2025-10-29 18:01 ` Philippe Mathieu-Daudé
2025-10-30 12:32 ` Anton Johansson via
2025-10-30 12:52 ` Philippe Mathieu-Daudé
2025-10-30 4:10 ` Alistair Francis
2025-10-27 12:35 ` [PATCH v2 3/3] hw/riscv: Widen OpenSBI dynamic info struct Anton Johansson via
2025-10-27 12:42 ` Philippe Mathieu-Daudé
2025-10-28 7:25 ` Philippe Mathieu-Daudé [this message]
2025-10-29 21:56 ` [PATCH v2 0/3] single-binary: Prepare hw/riscv for single compilation Philippe Mathieu-Daudé
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=494cb717-88eb-4243-a39c-62e94f89f285@linaro.org \
--to=philmd@linaro.org \
--cc=alistair.francis@wdc.com \
--cc=anjo@rev.ng \
--cc=palmer@dabbelt.com \
--cc=pierrick.bouvier@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).