From: Kevin Wolf <kwolf@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
Markus Armbruster <armbru@redhat.com>,
Michael Roth <michael.roth@amd.com>,
qemu-block@nongnu.org, Fiona Ebner <f.ebner@proxmox.com>,
Hanna Reitz <hreitz@redhat.com>
Subject: Re: [PATCH 1/3] iotests: add filter_qmp_generated_node_ids()
Date: Wed, 17 Jan 2024 17:13:18 +0100 [thread overview]
Message-ID: <Zaf8npvl1ideUgtF@redhat.com> (raw)
In-Reply-To: <20240116190042.1363717-2-stefanha@redhat.com>
Am 16.01.2024 um 20:00 hat Stefan Hajnoczi geschrieben:
> Add a filter function for QMP responses that contain QEMU's
> automatically generated node ids. The ids change between runs and must
> be masked in the reference output.
>
> The next commit will use this new function.
>
> Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
Reviewed-by: Kevin Wolf <kwolf@redhat.com>
next prev parent reply other threads:[~2024-01-17 16:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-16 19:00 [PATCH 0/3] monitor: only run coroutine commands in qemu_aio_context Stefan Hajnoczi
2024-01-16 19:00 ` [PATCH 1/3] iotests: add filter_qmp_generated_node_ids() Stefan Hajnoczi
2024-01-17 16:13 ` Kevin Wolf [this message]
2024-01-16 19:00 ` [PATCH 2/3] iotests: port 141 to Python for reliable QMP testing Stefan Hajnoczi
2024-01-17 16:13 ` Kevin Wolf
2024-01-17 18:04 ` Kevin Wolf
2024-01-18 14:55 ` Stefan Hajnoczi
2024-01-18 15:36 ` Kevin Wolf
2024-01-16 19:00 ` [PATCH 3/3] monitor: only run coroutine commands in qemu_aio_context Stefan Hajnoczi
2024-01-17 18:10 ` Kevin Wolf
2024-01-18 15:47 ` Fiona Ebner
2024-02-03 9:01 ` Michael Tokarev
2024-02-03 11:30 ` Michael Tokarev
2024-02-13 20:19 ` Stefan Hajnoczi
2024-01-18 11:20 ` [PATCH 0/3] " Michael Tokarev
2024-01-29 11:38 ` Peter Maydell
2024-02-03 2:19 ` YangHang Liu
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=Zaf8npvl1ideUgtF@redhat.com \
--to=kwolf@redhat.com \
--cc=armbru@redhat.com \
--cc=f.ebner@proxmox.com \
--cc=hreitz@redhat.com \
--cc=michael.roth@amd.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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 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).