From: Changlong Xie <xiecl.fnst@cn.fujitsu.com>
To: Alberto Garcia <berto@igalia.com>,
qemu devel <qemu-devel@nongnu.org>,
Eric Blake <eblake@redhat.com>, Kevin Wolf <kwolf@redhat.com>,
Max Reitz <mreitz@redhat.com>,
Markus Armbruster <armbru@redhat.com>
Cc: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v6 2/3] qmp event: Refactor QUORUM_REPORT_BAD
Date: Fri, 26 Feb 2016 09:20:29 +0800 [thread overview]
Message-ID: <56CFA85D.4060408@cn.fujitsu.com> (raw)
In-Reply-To: <w51mvqp12hn.fsf@maestria.local.igalia.com>
On 02/25/2016 06:57 PM, Alberto Garcia wrote:
> On Thu 25 Feb 2016 06:33:08 AM CET, Changlong Xie <xiecl.fnst@cn.fujitsu.com> wrote:
>> +Read/Write operation:
>> { "event": "QUORUM_REPORT_BAD",
>> - "data": { "node-name": "node0", "sector-num": 345435, "sectors-count": 5 },
>> + "data": { "node-name": "node0", "sector-num": 345435, "sectors-count": 5,
>> + "type": "read" },
>> "timestamp": { "seconds": 1344522075, "microseconds": 745528 } }
>
> Since you introduced the 'type' field and this is now an example of a
> read error, you can change the description to say simply "Read
> operation:". In my opinion there's no need to add yet another example
> for a write operation, I think it's clear enough.
Ok
>
>> +Flush operation:
>> +{ "event": "QUORUM_REPORT_BAD",
>> + "data": { "node-name": "node0", "sector-num": 0, "sectors-count": 2097120,
>> + "type": "flush", "error": "Broken pipe" },
>> + "timestamp": { "seconds": 1456406829, "microseconds": 291763 } }
>
> Here (and in the previous case) please indent "type" so it goes under
Surely.
> "node-name":
>
> { "event": "QUORUM_REPORT_BAD",
> "data": { "node-name": "node0", "sector-num": 0, "sectors-count": 2097120,
> "type": "flush", "error": "Broken pipe" },
> "timestamp": { "seconds": 1456406829, "microseconds": 291763 } }
>
> Otherwise I think the patch looks perfect now. Thanks!
>
Thanks for your review. Will send another series.
Thanks
-Xie
> Berto
>
>
> .
>
next prev parent reply other threads:[~2016-02-26 1:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-25 5:33 [Qemu-devel] [PATCH v6 0/3] modify vote rules for flush operation Changlong Xie
2016-02-25 5:33 ` [Qemu-devel] [PATCH v6 1/3] docs: fix invalid node name in qmp event Changlong Xie
2016-02-25 5:33 ` [Qemu-devel] [PATCH v6 2/3] qmp event: Refactor QUORUM_REPORT_BAD Changlong Xie
2016-02-25 10:57 ` Alberto Garcia
2016-02-26 1:20 ` Changlong Xie [this message]
2016-02-25 5:33 ` [Qemu-devel] [PATCH v6 3/3] quorum: modify vote rules for flush operation Changlong Xie
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=56CFA85D.4060408@cn.fujitsu.com \
--to=xiecl.fnst@cn.fujitsu.com \
--cc=armbru@redhat.com \
--cc=berto@igalia.com \
--cc=dgilbert@redhat.com \
--cc=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.