From: Kevin Wolf <kwolf@redhat.com>
To: Changlong Xie <xiecl.fnst@cn.fujitsu.com>
Cc: Alberto Garcia <berto@igalia.com>,
Markus Armbruster <armbru@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
qemu devel <qemu-devel@nongnu.org>, Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v7 0/3] modify vote rules for flush operation
Date: Tue, 1 Mar 2016 16:39:04 +0100 [thread overview]
Message-ID: <20160301153904.GH4250@noname.str.redhat.com> (raw)
In-Reply-To: <1456450742-13905-1-git-send-email-xiecl.fnst@cn.fujitsu.com>
Am 26.02.2016 um 02:38 hat Changlong Xie geschrieben:
> ChangLog:
> v7:
> 1. Fix coding style in doc/qmp-event.txt
> v6:
> 1. Make "type" mandatory for [PATCH 2/3]
> v5:
> 1. Fix invalid node name in docs/qmp-events.txt
> 2. Address comments from Eric, drop QUORUM_FLUSH_ERROR. Instead of reworking
> QUORUM_REPORT_BAD to make it compatible with quorum read/write/flush operations
> v4:
> 1. Introduce QUORUM_FLUSH_ERROR event to notify flush failure.
> v3:
> 1. *Note* that, the codes logic is different from what we talked in v2.
> I just keep flush interface the same logic as quorum read/write, and think
> it's reasoned.
>
> [Ref] http://lists.nongnu.org/archive/html/qemu-devel/2016-01/msg05342.html
Thanks, applied to the block branch.
Kevin
prev parent reply other threads:[~2016-03-01 15:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-26 1:38 [Qemu-devel] [PATCH v7 0/3] modify vote rules for flush operation Changlong Xie
2016-02-26 1:39 ` [Qemu-devel] [PATCH v7 1/3] docs: fix invalid node name in qmp event Changlong Xie
2016-02-26 1:39 ` [Qemu-devel] [PATCH v7 2/3] qmp event: Refactor QUORUM_REPORT_BAD Changlong Xie
2016-02-26 7:33 ` Alberto Garcia
2016-03-01 15:57 ` Eric Blake
2016-03-03 14:48 ` Alberto Garcia
2016-02-26 1:39 ` [Qemu-devel] [PATCH v7 3/3] quorum: modify vote rules for flush operation Changlong Xie
2016-03-01 15:39 ` Kevin Wolf [this message]
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=20160301153904.GH4250@noname.str.redhat.com \
--to=kwolf@redhat.com \
--cc=armbru@redhat.com \
--cc=berto@igalia.com \
--cc=dgilbert@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=xiecl.fnst@cn.fujitsu.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).