From: Markus Armbruster <armbru@redhat.com>
To: Steve Sistare <steven.sistare@oracle.com>
Cc: qemu-devel@nongnu.org, John Snow <jsnow@redhat.com>,
Cleber Rosa <crosa@redhat.com>, Eric Blake <eblake@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
"Daniel P. Berrange" <berrange@redhat.com>,
Eduardo Habkost <eduardo@habkost.net>,
Fabiano Rosas <farosas@suse.de>,
Laurent Vivier <lvivier@redhat.com>,
Philippe Mathieu-Daude <philmd@linaro.org>
Subject: Re: [PATCH V4 0/3] fast qom tree get
Date: Fri, 11 Jul 2025 17:06:08 +0200 [thread overview]
Message-ID: <87bjpqvkbj.fsf@pond.sub.org> (raw)
In-Reply-To: <1752164694-215567-1-git-send-email-steven.sistare@oracle.com> (Steve Sistare's message of "Thu, 10 Jul 2025 09:24:51 -0700")
This feels ready. Have a look at my (few) comments, and tell me what
you think. Happy to apply finishing touches in my tree, without another
respin.
Thanks your your patience!
next prev parent reply other threads:[~2025-07-11 15:13 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-10 16:24 [PATCH V4 0/3] fast qom tree get Steve Sistare
2025-07-10 16:24 ` [PATCH V4 1/3] qom: qom-list-get Steve Sistare
2025-07-11 14:35 ` Markus Armbruster
2025-07-11 15:22 ` Steven Sistare
2025-07-10 16:24 ` [PATCH V4 2/3] python: use qom-list-get Steve Sistare
2025-07-11 14:47 ` Markus Armbruster
2025-07-11 15:23 ` Steven Sistare
2025-07-11 16:50 ` Markus Armbruster
2025-07-11 17:08 ` Steven Sistare
2025-07-15 17:27 ` John Snow
2025-07-16 8:32 ` Markus Armbruster
2025-08-07 22:04 ` John Snow
2025-08-08 6:28 ` Markus Armbruster
2025-08-08 16:16 ` John Snow
2025-07-10 16:24 ` [PATCH V4 3/3] tests/qtest/qom-test: unit test for qom-list-getv Steve Sistare
2025-07-11 15:02 ` Markus Armbruster
2025-07-11 15:23 ` Steven Sistare
2025-07-11 15:06 ` Markus Armbruster [this message]
2025-07-11 15:27 ` [PATCH V4 0/3] fast qom tree get Steven Sistare
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=87bjpqvkbj.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=crosa@redhat.com \
--cc=eblake@redhat.com \
--cc=eduardo@habkost.net \
--cc=farosas@suse.de \
--cc=jsnow@redhat.com \
--cc=lvivier@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=steven.sistare@oracle.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.