From: Laszlo Ersek <lersek@redhat.com>
To: qemu-devel@nongnu.org, mdroth@linux.vnet.ibm.com, eblake@redhat.com
Subject: [Qemu-devel] [PATCH 2/2] qga schema: document generic QERR_UNSUPPORTED
Date: Fri, 15 Mar 2013 19:07:51 +0100 [thread overview]
Message-ID: <1363370871-10537-3-git-send-email-lersek@redhat.com> (raw)
In-Reply-To: <1363370871-10537-1-git-send-email-lersek@redhat.com>
Part of the wording was shamelessly stolen from Michael Roth's email.
Suggested-by: Michael Roth <mdroth@linux.vnet.ibm.com>
Signed-off-by: Laszlo Ersek <lersek@redhat.com>
---
qga/qapi-schema.json | 11 +++++++++++
1 files changed, 11 insertions(+), 0 deletions(-)
diff --git a/qga/qapi-schema.json b/qga/qapi-schema.json
index 2af3515..7155b7a 100644
--- a/qga/qapi-schema.json
+++ b/qga/qapi-schema.json
@@ -2,6 +2,17 @@
##
#
+# General note concerning the use of guest agent interfaces:
+#
+# "unsupported" is a higher-level error than the errors that individual
+# commands might document. The caller should always be prepared to receive
+# QERR_UNSUPPORTED, even if the given command doesn't specify it, or doesn't
+# document any failure mode at all.
+#
+##
+
+##
+#
# Echo back a unique integer value, and prepend to response a
# leading sentinel byte (0xFF) the client can check scan for.
#
--
1.7.1
next prev parent reply other threads:[~2013-03-15 18:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-15 18:07 [Qemu-devel] [PATCH 0/2] documentation fixups for the qga schema Laszlo Ersek
2013-03-15 18:07 ` [Qemu-devel] [PATCH 1/2] qga schema: mark optional GuestLogicalProcessor.can-offline with #optional Laszlo Ersek
2013-03-15 18:07 ` Laszlo Ersek [this message]
2013-03-15 18:36 ` [Qemu-devel] [PATCH 2/2] qga schema: document generic QERR_UNSUPPORTED mdroth
2013-03-15 18:11 ` [Qemu-devel] [PATCH 0/2] documentation fixups for the qga schema Eric Blake
2013-03-25 16:19 ` mdroth
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=1363370871-10537-3-git-send-email-lersek@redhat.com \
--to=lersek@redhat.com \
--cc=eblake@redhat.com \
--cc=mdroth@linux.vnet.ibm.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).