From: Fam Zheng <famz@redhat.com>
To: qemu-devel@nongnu.org, jcody@redhat.com
Cc: qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [Qemu-stable] [PATCH v2 0/2] backup: Fail early if cannot determine cluster size
Date: Tue, 24 May 2016 13:11:29 +0800 [thread overview]
Message-ID: <20160524051129.GA32476@ad.usersys.redhat.com> (raw)
In-Reply-To: <1463621147-12285-1-git-send-email-famz@redhat.com>
On Thu, 05/19 09:25, Fam Zheng wrote:
> v2: More accurately, s:hang:trigger assertion failure: in the bug fix patch
> commit message.
> Add John's and Jeff's R-b.
> Add a test. [Eric]
Jeff, will you take this series in your tree?
Fam
next prev parent reply other threads:[~2016-05-24 5:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-19 1:25 [Qemu-devel] [PATCH v2 0/2] backup: Fail early if cannot determine cluster size Fam Zheng
2016-05-19 1:25 ` [Qemu-devel] [PATCH v2 1/2] " Fam Zheng
2016-05-24 7:45 ` Kevin Wolf
2016-05-19 1:25 ` [Qemu-devel] [PATCH v2 2/2] iotests: Add regression test for drive-backup cluster size error Fam Zheng
2016-05-24 7:47 ` Kevin Wolf
2016-05-24 5:11 ` Fam Zheng [this message]
2016-05-24 13:40 ` [Qemu-devel] [PATCH v2 0/2] backup: Fail early if cannot determine cluster size Jeff Cody
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=20160524051129.GA32476@ad.usersys.redhat.com \
--to=famz@redhat.com \
--cc=jcody@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).