From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org
Cc: Anton Nefedov <anton.nefedov@virtuozzo.com>,
"Denis V. Lunev" <den@openvz.org>, Eric Blake <eblake@redhat.com>
Subject: [Qemu-devel] [PULL 17/17] qmp-events: fix GUEST_PANICKED description formatting
Date: Fri, 24 Feb 2017 18:40:30 +0100 [thread overview]
Message-ID: <1487958030-51417-18-git-send-email-pbonzini@redhat.com> (raw)
In-Reply-To: <1487958030-51417-1-git-send-email-pbonzini@redhat.com>
From: Anton Nefedov <anton.nefedov@virtuozzo.com>
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>
Message-Id: <1487614915-18710-4-git-send-email-den@openvz.org>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
---
qapi/event.json | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/qapi/event.json b/qapi/event.json
index 970ff02..e02852c 100644
--- a/qapi/event.json
+++ b/qapi/event.json
@@ -488,9 +488,9 @@
#
# @action: action that has been taken, currently always "pause"
#
-# @info: optional information about a panic
+# @info: #optional information about a panic (since 2.9)
#
-# Since: 1.5 (@info since 2.9)
+# Since: 1.5
#
# Example:
#
--
1.8.3.1
next prev parent reply other threads:[~2017-02-24 17:40 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-24 17:40 [Qemu-devel] [PULL 00/17] KVM and cpu-exec patches for 2.9 soft freeze Paolo Bonzini
2017-02-24 17:40 ` [Qemu-devel] [PULL 01/17] cpu-exec: unify icount_decr and tcg_exit_req Paolo Bonzini
2017-02-24 17:40 ` [Qemu-devel] [PULL 02/17] replay: check icount in cpu exec loop Paolo Bonzini
2017-02-24 17:40 ` [Qemu-devel] [PULL 03/17] cpu-exec: remove unnecessary check of cpu->exit_request Paolo Bonzini
2017-02-24 17:40 ` [Qemu-devel] [PULL 04/17] update-linux-headers: update for 4.11 Paolo Bonzini
2017-02-24 17:40 ` [Qemu-devel] [PULL 05/17] update Linux headers to 4.11 Paolo Bonzini
2017-02-24 17:40 ` [Qemu-devel] [PULL 06/17] cpus: remove ugly cast on sigbus_handler Paolo Bonzini
2017-02-24 17:40 ` [Qemu-devel] [PULL 07/17] KVM: x86: cleanup SIGBUS handlers Paolo Bonzini
2017-02-24 17:40 ` [Qemu-devel] [PULL 08/17] cpus: reorganize signal handling code Paolo Bonzini
2017-02-24 17:40 ` [Qemu-devel] [PULL 09/17] KVM: remove kvm_arch_on_sigbus Paolo Bonzini
2017-02-24 17:40 ` [Qemu-devel] [PULL 10/17] KVM: do not use sigtimedwait to catch SIGBUS Paolo Bonzini
2017-02-24 17:40 ` [Qemu-devel] [PULL 11/17] KVM: move SIG_IPI handling to kvm-all.c Paolo Bonzini
2017-02-24 17:40 ` [Qemu-devel] [PULL 12/17] kvm: use atomic_read/atomic_set to access cpu->exit_request Paolo Bonzini
2017-02-24 17:40 ` [Qemu-devel] [PULL 13/17] KVM: use KVM_CAP_IMMEDIATE_EXIT Paolo Bonzini
2017-02-24 17:40 ` [Qemu-devel] [PULL 14/17] vmxcap: port to Python 3 Paolo Bonzini
2017-02-24 17:40 ` [Qemu-devel] [PULL 15/17] vmxcap: update for September 2016 SDM Paolo Bonzini
2017-02-24 17:40 ` [Qemu-devel] [PULL 16/17] qapi: flatten GuestPanicInformation union Paolo Bonzini
2017-02-24 17:40 ` Paolo Bonzini [this message]
2017-02-24 18:27 ` [Qemu-devel] [PULL 00/17] KVM and cpu-exec patches for 2.9 soft freeze no-reply
2017-02-25 21:32 ` Peter Maydell
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=1487958030-51417-18-git-send-email-pbonzini@redhat.com \
--to=pbonzini@redhat.com \
--cc=anton.nefedov@virtuozzo.com \
--cc=den@openvz.org \
--cc=eblake@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).