From: Richard Henderson <richard.henderson@linaro.org>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>, qemu-devel@nongnu.org
Subject: Re: [PATCH v2 5/6] system/ramblock: Use ram_addr_t in ram_block_discard_range()
Date: Wed, 1 Oct 2025 14:05:57 -0700 [thread overview]
Message-ID: <2539cd05-e9e9-446f-93a2-188c3faa8948@linaro.org> (raw)
In-Reply-To: <20251001164456.3230-6-philmd@linaro.org>
On 10/1/25 09:44, Philippe Mathieu-Daudé wrote:
> Rename @start as @offset, since it express an offset within a RAMBlock.
>
> Signed-off-by: Philippe Mathieu-Daudé <philmd@linaro.org>
> ---
> include/system/ramblock.h | 3 ++-
> system/physmem.c | 20 ++++++++++----------
> 2 files changed, 12 insertions(+), 11 deletions(-)
The patch subject is now wrong. Otherwise,
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
r~
next prev parent reply other threads:[~2025-10-01 21:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-01 16:44 [PATCH v2 0/6] system/ramblock: Sanitize header Philippe Mathieu-Daudé
2025-10-01 16:44 ` [PATCH v2 1/6] system/ramblock: Remove obsolete comment Philippe Mathieu-Daudé
2025-10-01 21:02 ` Richard Henderson
2025-10-01 16:44 ` [PATCH v2 2/6] system/ramblock: Move ram_block_is_pmem() declaration Philippe Mathieu-Daudé
2025-10-01 21:03 ` Richard Henderson
2025-10-01 16:44 ` [PATCH v2 3/6] system/ramblock: Move ram_block_discard_*_range() declarations Philippe Mathieu-Daudé
2025-10-01 21:04 ` Richard Henderson
2025-10-01 16:44 ` [PATCH v2 4/6] system/ramblock: Use ram_addr_t in ram_block_discard_guest_memfd_range Philippe Mathieu-Daudé
2025-10-01 21:05 ` Richard Henderson
2025-10-01 16:44 ` [PATCH v2 5/6] system/ramblock: Use ram_addr_t in ram_block_discard_range() Philippe Mathieu-Daudé
2025-10-01 21:05 ` Richard Henderson [this message]
2025-10-01 16:44 ` [PATCH v2 6/6] system/ramblock: Move RAMBlock helpers out of "system/ram_addr.h" 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=2539cd05-e9e9-446f-93a2-188c3faa8948@linaro.org \
--to=richard.henderson@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.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).