From: Kevin Wolf <kwolf@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org, mreitz@redhat.com
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH v4 0/4] more blkdebug tweaks
Date: Tue, 6 Jun 2017 14:26:45 +0200 [thread overview]
Message-ID: <20170606122645.GC5448@noname.redhat.com> (raw)
In-Reply-To: <20170605203845.24351-1-eblake@redhat.com>
Am 05.06.2017 um 22:38 hat Eric Blake geschrieben:
> I found a crasher and some odd behavior while rebasing my
> bdrv_get_block_status series, so I figured I'd get these things
> fixed first. This is based on top of Max's block branch.
>
> Available as a tag at:
> git fetch git://repo.or.cz/qemu/ericb.git nbd-blkdebug-status-v4
>
> Since v3:
> - check all qemu-iotests (patch 1)
Whoops, somehow I ended up applying and reviewing v4 while looking at
the v3 thread... Looks like there really aren't any missing test case
updates any more.
Thanks, applied to the block branch.
Kevin
next prev parent reply other threads:[~2017-06-06 12:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-05 20:38 [Qemu-devel] [PATCH v4 0/4] more blkdebug tweaks Eric Blake
2017-06-05 20:38 ` [Qemu-devel] [PATCH v4 1/4] qemu-io: Don't die on second open Eric Blake
2017-06-06 0:52 ` John Snow
2017-06-05 20:38 ` [Qemu-devel] [PATCH v4 2/4] block: Guarantee that *file is set on bdrv_get_block_status() Eric Blake
2017-06-06 0:52 ` John Snow
2017-06-05 20:38 ` [Qemu-devel] [PATCH v4 3/4] block: Simplify use of BDRV_BLOCK_RAW Eric Blake
2017-06-06 2:49 ` Fam Zheng
2017-06-05 20:38 ` [Qemu-devel] [PATCH v4 4/4] blkdebug: Support .bdrv_co_get_block_status Eric Blake
2017-06-06 4:11 ` [Qemu-devel] [PATCH v4 0/4] more blkdebug tweaks John Snow
2017-06-06 12:26 ` Kevin Wolf [this message]
2017-06-27 16:01 ` [Qemu-devel] [Qemu-block] " Eric Blake
2017-06-27 18:41 ` Kevin Wolf
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=20170606122645.GC5448@noname.redhat.com \
--to=kwolf@redhat.com \
--cc=eblake@redhat.com \
--cc=mreitz@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).