From: Max Reitz <mreitz@redhat.com>
To: qemu-block@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
qemu-devel@nongnu.org, Max Reitz <mreitz@redhat.com>
Subject: [PATCH 0/2] iotests/291: Two fixes
Date: Tue, 27 Oct 2020 17:44:14 +0100 [thread overview]
Message-ID: <20201027164416.144115-1-mreitz@redhat.com> (raw)
Hi,
This series fixes two things about 291, one of which is actually a
problem right now (patch 1), and one of which is more or less of a style
question currently, but will become a problem with my FUSE export series
(patch 2).
(The issues were different enough that I decided to split the fixes into
two patches.)
Max Reitz (2):
iotests/291: Filter irrelevant parts of img-info
iotests/291: Stop NBD server
tests/qemu-iotests/291 | 16 +++++++++++++---
tests/qemu-iotests/291.out | 20 --------------------
2 files changed, 13 insertions(+), 23 deletions(-)
--
2.26.2
next reply other threads:[~2020-10-27 16:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-27 16:44 Max Reitz [this message]
2020-10-27 16:44 ` [PATCH 1/2] iotests/291: Filter irrelevant parts of img-info Max Reitz
2020-10-27 16:44 ` [PATCH 2/2] iotests/291: Stop NBD server Max Reitz
2020-10-27 17:20 ` [PATCH 0/2] iotests/291: Two fixes Eric Blake
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=20201027164416.144115-1-mreitz@redhat.com \
--to=mreitz@redhat.com \
--cc=kwolf@redhat.com \
--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).