All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Denis V. Lunev" <den@openvz.org>
To: qemu-devel@nongnu.org
Cc: den@openvz.org, Anton Nefedov <anton.nefedov@virtuozzo.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Eric Blake <eblake@redhat.com>
Subject: [Qemu-devel] [PATCH for 2.9 0/3] guest panic information follow-up
Date: Mon, 20 Feb 2017 21:21:52 +0300	[thread overview]
Message-ID: <1487614915-18710-1-git-send-email-den@openvz.org> (raw)

This is a set of followup patches requested by Eric Blake.

Signed-off-by: Anton Nefedov <anton.nefedov@virtuozzo.com>
Signed-off-by: Denis V. Lunev <den@openvz.org>
CC: Paolo Bonzini <pbonzini@redhat.com>
CC: Eric Blake <eblake@redhat.com>

Anton Nefedov (3):
  i386/cpu: release GuestPanicInformation memory
  qapi: flatten GuestPanicInformation union
  qmp-events: fix GUEST_PANICKED description formatting

 kvm-all.c         |  5 ++++-
 qapi-schema.json  | 12 ++++++++++++
 qapi/event.json   |  4 ++--
 target/i386/cpu.c | 15 ++++++---------
 vl.c              | 22 +++++++++-------------
 5 files changed, 33 insertions(+), 25 deletions(-)

-- 
2.7.4

             reply	other threads:[~2017-02-20 18:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-20 18:21 Denis V. Lunev [this message]
2017-02-20 18:21 ` [Qemu-devel] [PATCH 1/3] i386/cpu: release GuestPanicInformation memory Denis V. Lunev
2017-02-20 19:42   ` Eric Blake
2017-02-20 18:21 ` [Qemu-devel] [PATCH 2/3] qapi: flatten GuestPanicInformation union Denis V. Lunev
2017-02-20 19:48   ` Eric Blake
2017-02-20 19:58     ` Denis V. Lunev
2017-02-21  8:15       ` Evgeny Yakovlev
2017-02-20 18:21 ` [Qemu-devel] [PATCH 3/3] qmp-events: fix GUEST_PANICKED description formatting Denis V. Lunev
2017-02-20 19:49   ` Eric Blake
2017-02-21 10:41 ` [Qemu-devel] [PATCH for 2.9 0/3] guest panic information follow-up Paolo Bonzini

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=1487614915-18710-1-git-send-email-den@openvz.org \
    --to=den@openvz.org \
    --cc=anton.nefedov@virtuozzo.com \
    --cc=eblake@redhat.com \
    --cc=pbonzini@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.