From: Alon Levy <alevy@redhat.com>
To: qemu-devel@nongnu.org, lcapitulino@redhat.com, kraxel@redhat.com,
armbru@redhat.com
Subject: [Qemu-devel] [PATCH 1/4] qapi-schema: fix typos and explain 'spice' auth
Date: Fri, 24 Feb 2012 23:22:02 +0200 [thread overview]
Message-ID: <1330118525-14522-1-git-send-email-alevy@redhat.com> (raw)
Signed-off-by: Alon Levy <alevy@redhat.com>
---
qapi-schema.json | 18 ++++++++++--------
1 files changed, 10 insertions(+), 8 deletions(-)
diff --git a/qapi-schema.json b/qapi-schema.json
index d0b6792..72b17f1 100644
--- a/qapi-schema.json
+++ b/qapi-schema.json
@@ -616,12 +616,13 @@
# @connection-id: SPICE connection id number. All channels with the same id
# belong to the same SPICE session.
#
-# @connection-type: SPICE channel type number. "1" is the main control channel,
-# filter for this one if you want track spice sessions only
+# @connection-type: SPICE channel type number. "1" is the main control
+# channel, filter for this one if you want to track spice
+# sessions only
#
-# @channel-id: SPICE channel ID number. Usually "0", might be different needed
-# when multiple channels of the same type exist, such as multiple
-# display channels in a multihead setup
+# @channel-id: SPICE channel ID number. Usually "0", might be different when
+# multiple channels of the same type exist, such as multiple
+# display channels in a multihead setup
#
# @tls: true if the channel is encrypted, false otherwise.
#
@@ -649,8 +650,9 @@
# @tls-port: #optional The SPICE server's TLS port number.
#
# @auth: #optional the current authentication type used by the server
-# 'none' if no authentication is being used
-# 'spice' (TODO: describe)
+# 'none' if no authentication is being used
+# 'spice' uses SASL or direct TLS authentication, depending on command
+# line options
#
# @channels: a list of @SpiceChannel for each active spice channel
#
@@ -1216,7 +1218,7 @@
{ 'command': 'migrate_set_speed', 'data': {'value': 'int'} }
##
-# @DevicePropertyInfo:
+# @ObjectPropertyInfo:
#
# @name: the name of the property
#
--
1.7.9.1
next reply other threads:[~2012-02-24 21:22 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-24 21:22 Alon Levy [this message]
2012-02-24 21:22 ` [Qemu-devel] [PATCH 2/4] qjson.h: include compiler.h for GCC_FMT_ATTR Alon Levy
2012-02-28 19:58 ` Luiz Capitulino
2012-02-28 20:49 ` Alon Levy
2012-02-24 21:22 ` [Qemu-devel] [PATCH 3/4] monitor, console: add QEVENT_SCREEN_DUMP_COMPLETE Alon Levy
2012-02-28 20:01 ` Luiz Capitulino
2012-02-28 20:51 ` Alon Levy
2012-02-29 14:38 ` Luiz Capitulino
2012-02-24 21:22 ` [Qemu-devel] [PATCH 4/4] add qmp screendump-async Alon Levy
2012-02-24 22:40 ` Anthony Liguori
2012-02-25 8:46 ` Alon Levy
2012-02-28 20:10 ` Luiz Capitulino
2012-02-29 7:49 ` Gerd Hoffmann
2012-02-29 14:52 ` Luiz Capitulino
2012-02-29 8:15 ` Alon Levy
2012-02-29 14:58 ` Luiz Capitulino
2012-02-29 15:37 ` Alon Levy
2012-02-28 20:05 ` Luiz Capitulino
2012-02-29 8:39 ` Alon Levy
2012-02-29 14:59 ` Luiz Capitulino
2012-03-05 13:40 ` Alon Levy
2012-03-05 13:45 ` Alon Levy
2012-02-28 8:05 ` [Qemu-devel] [PATCH 1/4] qapi-schema: fix typos and explain 'spice' auth Alon Levy
2012-02-28 19:57 ` Luiz Capitulino
2012-02-29 8:40 ` Alon Levy
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=1330118525-14522-1-git-send-email-alevy@redhat.com \
--to=alevy@redhat.com \
--cc=armbru@redhat.com \
--cc=kraxel@redhat.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).