From: Hanna Reitz <hreitz@redhat.com>
To: John Snow <jsnow@redhat.com>, Kevin Wolf <kwolf@redhat.com>
Cc: Eduardo Habkost <eduardo@habkost.net>,
Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
qemu-devel <qemu-devel@nongnu.org>,
Qemu-block <qemu-block@nongnu.org>,
Cleber Rosa <crosa@redhat.com>
Subject: Re: [PATCH 0/4] iotests: finalize switch to async QMP
Date: Fri, 18 Mar 2022 17:32:44 +0100 [thread overview]
Message-ID: <cac97a40-6dd6-2ede-d7f0-c7b198d44c7c@redhat.com> (raw)
In-Reply-To: <CAFn=p-bL4XoZMajFffM9LKtFZBKj8W=x2qMQAiewSxLJAP7Qfw@mail.gmail.com>
On 08.02.22 20:52, John Snow wrote:
> Squeak Squeak...
>
> ...Any objections to me staging this?
>
> (This patchset removes the accommodations in iotests for allowing
> either library to run and always forces the new one. Point of no
> return for iotests.)
I took this as “if I don’t reply, that’ll be reply enough” :)
Looks to me like the rebase is minimal (just shuffling the imports in
patch 4 a bit), so I guess this’ll help even before you resend:
Acked-by: Hanna Reitz <hreitz@redhat.com>
next prev parent reply other threads:[~2022-03-18 16:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-03 2:24 [PATCH 0/4] iotests: finalize switch to async QMP John Snow
2022-02-03 2:24 ` [PATCH 1/4] python/machine: permanently switch to AQMP John Snow
2022-02-03 2:24 ` [PATCH 2/4] scripts/bench-block-job: " John Snow
2022-02-03 2:24 ` [PATCH 3/4] iotests/mirror-top-perms: " John Snow
2022-02-04 8:42 ` Vladimir Sementsov-Ogievskiy
2022-02-03 2:24 ` [PATCH 4/4] iotests: " John Snow
2022-02-08 19:52 ` [PATCH 0/4] iotests: finalize switch to async QMP John Snow
2022-03-18 16:32 ` Hanna Reitz [this message]
2022-03-18 17:35 ` John Snow
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=cac97a40-6dd6-2ede-d7f0-c7b198d44c7c@redhat.com \
--to=hreitz@redhat.com \
--cc=crosa@redhat.com \
--cc=eduardo@habkost.net \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@virtuozzo.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).