From: Peter Xu <peterx@redhat.com>
To: Juan Quintela <quintela@redhat.com>
Cc: qemu-devel@nongnu.org, dgilbert@redhat.com, lvivier@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2] migration: Pass Error ** argument to {save, load}_vmstate
Date: Fri, 12 May 2017 11:00:47 +0800 [thread overview]
Message-ID: <20170512030047.GL28293@pxdev.xzpeter.org> (raw)
In-Reply-To: <20170511153440.6475-1-quintela@redhat.com>
On Thu, May 11, 2017 at 05:34:40PM +0200, Juan Quintela wrote:
> This way we use the "normal" way of printing errors for hmp commands.
>
> Signed-off-by: Juan Quintela <quintela@redhat.com>
> Suggested-by: Paolo Bonzini <pbonzini@redhat.com>
Reviewed-by: Peter Xu <peterx@redhat.com>
--
Peter Xu
prev parent reply other threads:[~2017-05-12 3:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-11 15:34 [Qemu-devel] [PATCH v2] migration: Pass Error ** argument to {save, load}_vmstate Juan Quintela
2017-05-11 16:34 ` Laurent Vivier
2017-05-12 3:00 ` Peter Xu [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=20170512030047.GL28293@pxdev.xzpeter.org \
--to=peterx@redhat.com \
--cc=dgilbert@redhat.com \
--cc=lvivier@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@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).