From: Peter Xu <peterx@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>
Cc: qemu-devel@nongnu.org, David Hildenbrand <david@redhat.com>,
"Maciej S. Szmigiero" <maciej.szmigiero@oracle.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Richard Henderson <richard.henderson@linaro.org>,
kvm@vger.kernel.org, "Michael S. Tsirkin" <mst@redhat.com>,
Fabiano Rosas <farosas@suse.de>
Subject: Re: [PATCH v3 0/5] system/ramblock: Sanitize header
Date: Thu, 2 Oct 2025 10:43:29 -0400 [thread overview]
Message-ID: <aN6Pkeu_tb5giiPc@x1.local> (raw)
In-Reply-To: <20251002032812.26069-1-philmd@linaro.org>
On Thu, Oct 02, 2025 at 05:28:07AM +0200, Philippe Mathieu-Daudé wrote:
> (series fully reviewed, I plan to merge via my tree)
>
> Usual API cleanups, here focusing on RAMBlock API:
> move few prototypes out of "exec/cpu-common.h" and
> "system/ram_addr.h" to "system/ramblock.h".
Acked-by: Peter Xu <peterx@redhat.com>
--
Peter Xu
next prev parent reply other threads:[~2025-10-02 14:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-02 3:28 [PATCH v3 0/5] system/ramblock: Sanitize header Philippe Mathieu-Daudé
2025-10-02 3:28 ` [PATCH v3 1/5] system/ramblock: Remove obsolete comment Philippe Mathieu-Daudé
2025-10-02 3:28 ` [PATCH v3 2/5] system/ramblock: Move ram_block_is_pmem() declaration Philippe Mathieu-Daudé
2025-10-02 3:28 ` [PATCH v3 3/5] system/ramblock: Move ram_block_discard_*_range() declarations Philippe Mathieu-Daudé
2025-10-02 3:28 ` [PATCH v3 4/5] system/ramblock: Rename @start -> @offset in ram_block_discard_range() Philippe Mathieu-Daudé
2025-10-02 3:28 ` [PATCH v3 5/5] system/ramblock: Move RAMBlock helpers out of "system/ram_addr.h" Philippe Mathieu-Daudé
2025-10-02 14:43 ` Peter Xu [this message]
2025-10-03 20:37 ` [PATCH v3 0/5] system/ramblock: Sanitize header 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=aN6Pkeu_tb5giiPc@x1.local \
--to=peterx@redhat.com \
--cc=david@redhat.com \
--cc=farosas@suse.de \
--cc=kvm@vger.kernel.org \
--cc=maciej.szmigiero@oracle.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@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