From: Amos Kong <akong@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: Luiz Capitulino <lcapitulino@redhat.com>,
qemu-devel@nongnu.org, Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] input: move input-send-event into experimental namespace
Date: Tue, 25 Nov 2014 15:57:34 +0800 [thread overview]
Message-ID: <20141125075734.GB11690@air.redhat.com> (raw)
In-Reply-To: <1416899934-13952-1-git-send-email-kraxel@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2424 bytes --]
On Tue, Nov 25, 2014 at 08:18:54AM +0100, Gerd Hoffmann wrote:
> Ongoing discussions on how we are going to specify the console,
> so tag the command as experiemntal so we can refine things in
> the 2.3 development cycle.
%s/experiemntal/experimental/
Reviewed-by: Amos Kong <akong@redhat.com>
> Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
> ---
> qmp-commands.hx | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/qmp-commands.hx b/qmp-commands.hx
> index 8812401..d6b7362 100644
> --- a/qmp-commands.hx
> +++ b/qmp-commands.hx
> @@ -3791,13 +3791,13 @@ Example:
> EQMP
>
> {
> - .name = "input-send-event",
> + .name = "x-input-send-event",
> .args_type = "console:i?,events:q",
> .mhandler.cmd_new = qmp_marshal_input_input_send_event,
> },
>
> SQMP
> -@input-send-event
> +@x-input-send-event
> -----------------
>
> Send input event to guest.
> @@ -3815,13 +3815,13 @@ Example (1):
>
> Press left mouse button.
>
> --> { "execute": "input-send-event",
> +-> { "execute": "x-input-send-event",
> "arguments": { "console": 0,
> "events": [ { "type": "btn",
> "data" : { "down": true, "button": "Left" } } } }
(not problem of this patch)
typo, lack of ']'
> <- { "return": {} }
>
> --> { "execute": "input-send-event",
> +-> { "execute": "x-input-send-event",
> "arguments": { "console": 0,
> "events": [ { "type": "btn",
> "data" : { "down": false, "button": "Left" } } } }
some typo.
> @@ -3831,7 +3831,7 @@ Example (2):
>
> Press ctrl-alt-del.
>
> --> { "execute": "input-send-event",
> +-> { "execute": "x-input-send-event",
> "arguments": { "console": 0, "events": [
> { "type": "key", "data" : { "down": true,
> "key": {"type": "qcode", "data": "ctrl" } } },
> @@ -3845,7 +3845,7 @@ Example (3):
>
> Move mouse pointer to absolute coordinates (20000, 400).
>
> --> { "execute": "input-send-event" ,
> +-> { "execute": "x-input-send-event" ,
> "arguments": { "console": 0, "events": [
> { "type": "abs", "data" : { "axis": "X", "value" : 20000 } },
> { "type": "abs", "data" : { "axis": "Y", "value" : 400 } } ] } }
> --
> 1.8.3.1
>
--
Amos.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-11-25 7:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-25 7:18 [Qemu-devel] [PATCH] input: move input-send-event into experimental namespace Gerd Hoffmann
2014-11-25 7:57 ` Amos Kong [this message]
2014-11-25 8:06 ` Markus Armbruster
2014-11-25 8:37 ` Amos Kong
2014-11-25 11:58 ` Markus Armbruster
2014-11-25 13:55 ` Markus Armbruster
2014-11-25 16:35 ` Eric Blake
2014-11-26 6:21 ` Amos Kong
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=20141125075734.GB11690@air.redhat.com \
--to=akong@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).