From: Fam Zheng <fam@euphon.net>
To: Fam Zheng <famz@redhat.com>
Cc: kwolf@redhat.com, pbonzini@redhat.com, stefanha@redhat.com,
qemu-devel@nongnu.org, qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v3 05/12] block: Introduce "drained begin/end" API
Date: Mon, 19 Oct 2015 07:22:37 +0800 [thread overview]
Message-ID: <E1ZnxUc-0002yS-DU@eggs.gnu.org> (raw)
I should have updated bdrv_move_feature_bits as Kevin pointed out in the previous revision. I'll rebase on to the pull req that removes bdrv_swap anyway.
Thanks,
Fam
next reply other threads:[~2015-10-18 23:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-18 23:22 Fam Zheng [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-10-16 10:12 [Qemu-devel] [PATCH v3 00/12] block: Protect nested event loop with bdrv_drained_begin and bdrv_drained_end Fam Zheng
2015-10-16 10:12 ` [Qemu-devel] [PATCH v3 05/12] block: Introduce "drained begin/end" API Fam Zheng
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=E1ZnxUc-0002yS-DU@eggs.gnu.org \
--to=fam@euphon.net \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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).