From: Eric Blake <eblake@redhat.com>
To: qemu-devel@nongnu.org
Cc: armbru@redhat.com, alistair.francis@xilinx.com
Subject: Re: [Qemu-devel] [PATCH v4 0/4] event: Add source information to SHUTDOWN
Date: Thu, 27 Apr 2017 17:37:08 -0500 [thread overview]
Message-ID: <8c8261bd-d854-cf32-9fab-011c11e3afb5@redhat.com> (raw)
In-Reply-To: <20170427213202.13512-1-eblake@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1008 bytes --]
On 04/27/2017 04:31 PM, Eric Blake wrote:
> v2 was here:
> https://lists.gnu.org/archive/html/qemu-devel/2017-04/msg03185.html
> v3 was here:
> https://lists.gnu.org/archive/html/qemu-devel/2017-04/msg05515.html
>
> Since then:
> - s/ShutdownType/ShutdownCause/ to avoid conflict with mingw header pollution
> - fix long line
>
> Eric Blake (4):
> shutdown: Simplify shutdown_signal
> shutdown: Prepare for use of an enum in reset/shutdown_request
> shutdown: Add source information to SHUTDOWN and RESET
> RFC: shutdown: Expose full ShutdownCause across QMP
>
> qapi-schema.json | 26 +
> qapi/event.json | 12 +-
> include/sysemu/sysemu.h | 6 +-
> trace/generated-tracers.h | 18523 ++++++++++++++++++++++++++++++++++++++++++
Bleargh. I 'git add'ed too much. Apologies for the spam. v5 coming up.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
prev parent reply other threads:[~2017-04-27 22:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-27 21:31 [Qemu-devel] [PATCH v4 0/4] event: Add source information to SHUTDOWN Eric Blake
2017-04-27 21:31 ` [Qemu-devel] [PATCH v4 1/4] shutdown: Simplify shutdown_signal Eric Blake
2017-04-27 21:32 ` [Qemu-devel] [PATCH v4 2/4] shutdown: Prepare for use of an enum in reset/shutdown_request Eric Blake
2017-04-27 21:32 ` [Qemu-devel] [PATCH v4 4/4] RFC: shutdown: Expose full ShutdownCause across QMP Eric Blake
2017-04-27 22:37 ` 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=8c8261bd-d854-cf32-9fab-011c11e3afb5@redhat.com \
--to=eblake@redhat.com \
--cc=alistair.francis@xilinx.com \
--cc=armbru@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).