From: Peter Xu <peterx@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel@nongnu.org, "Paolo Bonzini" <pbonzini@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Li Zhijian" <lizhijian@fujitsu.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Fabiano Rosas" <farosas@suse.de>,
"Zhang Chen" <zhangckid@gmail.com>,
"Juraj Marcin" <jmarcin@redhat.com>,
"Jason Wang" <jasowang@redhat.com>
Subject: Re: [PATCH 0/3] Three small fixes over qom-list-properties crash
Date: Tue, 28 Apr 2026 11:36:16 -0400 [thread overview]
Message-ID: <afDT8OhOB6UM_Xd7@x1.local> (raw)
In-Reply-To: <87h5p0vo38.fsf@pond.sub.org>
On Fri, Apr 24, 2026 at 09:01:31AM +0200, Markus Armbruster wrote:
> Peter Xu <peterx@redhat.com> writes:
>
> > Markus's report is here:
> >
> > https://lore.kernel.org/r/87a4uvw066.fsf@pond.sub.org
> >
> > These three that are relevant to either migration or memory, so I had a
> > look.
>
> Thank you!
>
> Series
> Tested-by: Markus Armbruster <armbru@redhat.com>
>
> Suggest to include the reproducer in the commit messages.
>
I saw Marc-André sent a more comprehensive series; I'll drop this one then.
Thanks for taking a look.
--
Peter Xu
prev parent reply other threads:[~2026-04-28 15:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-23 18:32 [PATCH 0/3] Three small fixes over qom-list-properties crash Peter Xu
2026-04-23 18:32 ` [PATCH 1/3] colo-compare: Fix QMP qom-list-properties crashing Peter Xu
2026-04-23 18:32 ` [PATCH 2/3] system/ioport: Fix qom-list-properties crash on portio list obj Peter Xu
2026-04-23 18:32 ` [PATCH 3/3] qio: Fix qom-list-properties crash on net listener object Peter Xu
2026-04-23 19:34 ` Daniel P. Berrangé
2026-04-24 7:01 ` [PATCH 0/3] Three small fixes over qom-list-properties crash Markus Armbruster
2026-04-28 15:36 ` Peter Xu [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=afDT8OhOB6UM_Xd7@x1.local \
--to=peterx@redhat.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=farosas@suse.de \
--cc=jasowang@redhat.com \
--cc=jmarcin@redhat.com \
--cc=lizhijian@fujitsu.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=zhangckid@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.