qemu-trivial.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Hailiang Zhang <zhang.zhanghailiang@huawei.com>
To: Eric Blake <eblake@redhat.com>, <armbru@redhat.com>
Cc: <qemu-devel@nongnu.org>, <qemu-trivial@nongnu.org>
Subject: Re: [Qemu-trivial] [PATCH v2] qapi-schema: clarify 'colo' state for MigrationStatus
Date: Mon, 14 Nov 2016 10:36:45 +0800	[thread overview]
Message-ID: <5829233D.8080709@huawei.com> (raw)
In-Reply-To: <f1f826e3-49b6-1755-24fe-ea96d8d484b1@redhat.com>

ping ?

Anyone pick this up?

On 2016/11/2 22:04, Eric Blake wrote:
> On 11/02/2016 02:44 AM, zhanghailiang wrote:
>> VM can not get into colo state unless users enable 'x-colo'
>> capability for migration, Here it is necessary to clarify
>> this.
>>
>> Suggested-by: Eric Blake <eblake@redhat.com>
>> Signed-off-by: zhanghailiang <zhang.zhanghailiang@huawei.com>
>> ---
>> v2:
>> - Clarify colo state for RunState too as Eric suggested.
>> ---
>>   qapi-schema.json | 8 +++++---
>>   1 file changed, 5 insertions(+), 3 deletions(-)
>
> Reviewed-by: Eric Blake <eblake@redhat.com>
>
>



  reply	other threads:[~2016-11-14  2:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-02  7:44 [Qemu-trivial] [PATCH v2] qapi-schema: clarify 'colo' state for MigrationStatus zhanghailiang
2016-11-02 14:04 ` Eric Blake
2016-11-14  2:36   ` Hailiang Zhang [this message]
2016-11-14 13:54     ` [Qemu-trivial] [Qemu-devel] " Stefan Hajnoczi
2016-11-15  6:12       ` Hailiang Zhang
2016-11-15  8:44       ` Laurent Vivier
2016-11-15  8:58         ` Zhang Chen
2016-11-15  9:03           ` Hailiang Zhang
2016-11-15  9:10             ` Zhang Chen
2016-11-17  7:08         ` Hailiang Zhang
2016-11-17  7:52           ` Laurent Vivier
2016-11-17 10:07             ` Stefan Hajnoczi

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=5829233D.8080709@huawei.com \
    --to=zhang.zhanghailiang@huawei.com \
    --cc=armbru@redhat.com \
    --cc=eblake@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@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).