From: Eric Blake <eblake@redhat.com>
To: Chen Hanxiao <chen_han_xiao@126.com>,
Luiz Capitulino <lcapitulino@redhat.com>,
Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2 2/2] hmp: add support for system_suspend
Date: Mon, 30 Nov 2015 11:12:27 -0700 [thread overview]
Message-ID: <565C918B.4040504@redhat.com> (raw)
In-Reply-To: <1448679706-23771-3-git-send-email-chen_han_xiao@126.com>
[-- Attachment #1: Type: text/plain, Size: 961 bytes --]
On 11/27/2015 08:01 PM, Chen Hanxiao wrote:
> From: Chen Hanxiao <chenhanxiao@gmail.com>
>
> This patch add support for system_suspend hmp command.
>
> Signed-off-by: Chen Hanxiao <chenhanxiao@gmail.com>
> ---
> hmp-commands.hx | 14 ++++++++++++++
> hmp.c | 5 +++++
> hmp.h | 1 +
> 3 files changed, 20 insertions(+)
>
> +++ b/hmp.c
> @@ -885,6 +885,11 @@ void hmp_system_powerdown(Monitor *mon, const QDict *qdict)
> qmp_system_powerdown(NULL);
> }
>
> +void hmp_system_suspend(Monitor *mon, const QDict *qdict)
> +{
> + qmp_system_suspend(NULL);
Why are you ignoring any potential errors? Wouldn't it be better to
report an error, if one occurs? Or at least pass &error_abort to assert
that no error can occur (matching the current implementation in patch
1/2 that never fails).
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
prev parent reply other threads:[~2015-11-30 18:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-28 3:01 [Qemu-devel] [PATCH v2 0/2] qmp/hmp: add support for system_suspend Chen Hanxiao
2015-11-28 3:01 ` [Qemu-devel] [PATCH v2 1/2] qmp: " Chen Hanxiao
2015-11-30 18:10 ` Eric Blake
2015-12-01 14:41 ` Chen Hanxiao
2015-11-28 3:01 ` [Qemu-devel] [PATCH v2 2/2] hmp: " Chen Hanxiao
2015-11-30 18:12 ` Eric Blake [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=565C918B.4040504@redhat.com \
--to=eblake@redhat.com \
--cc=armbru@redhat.com \
--cc=chen_han_xiao@126.com \
--cc=lcapitulino@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 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).