From: Thomas Huth <thuth@redhat.com>
To: Peter Xu <peterx@redhat.com>,
qemu-devel@nongnu.org, Qemu-block <qemu-block@nongnu.org>
Cc: Fabiano Rosas <farosas@suse.de>,
Peter Maydell <peter.maydell@linaro.org>,
Pierrick Bouvier <pierrick.bouvier@linaro.org>
Subject: Re: [PATCH] migration: Check current_migration in migration_is_running()
Date: Wed, 6 Nov 2024 10:43:22 +0100 [thread overview]
Message-ID: <f11c663c-49c4-439a-a20d-baccbc1e0756@redhat.com> (raw)
In-Reply-To: <20241105182725.2393425-1-peterx@redhat.com>
On 05/11/2024 19.27, Peter Xu wrote:
> Report shows that commit 34a8892dec broke iotest 055:
>
> https://lore.kernel.org/r/b8806360-a2b6-4608-83a3-db67e264c733@linaro.org
FWIW, this patch also fixes a lot of other broken iotests (vmdk and vpc)
that occur when running "make check SPEED=thorough".
Tested-by: Thomas Huth <thuth@redhat.com>
next prev parent reply other threads:[~2024-11-06 9:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-05 18:27 [PATCH] migration: Check current_migration in migration_is_running() Peter Xu
2024-11-05 18:31 ` Pierrick Bouvier
2024-11-05 20:45 ` Fabiano Rosas
2024-11-06 9:43 ` Thomas Huth [this message]
2024-11-06 17:18 ` Pierrick Bouvier
2024-11-06 17:42 ` Thomas Huth
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=f11c663c-49c4-439a-a20d-baccbc1e0756@redhat.com \
--to=thuth@redhat.com \
--cc=farosas@suse.de \
--cc=peter.maydell@linaro.org \
--cc=peterx@redhat.com \
--cc=pierrick.bouvier@linaro.org \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).