From: Amos Kong <akong@redhat.com>
To: qemu-devel@nongnu.org
Cc: aliguori@us.ibm.com, eblake@redhat.com, lcapitulino@redhat.com
Subject: [Qemu-devel] [PATCH v8 0/7] convert sendkey to qapi
Date: Fri, 31 Aug 2012 10:56:19 +0800 [thread overview]
Message-ID: <1346381786-18626-1-git-send-email-akong@redhat.com> (raw)
This series converted 'sendkey' command to qapi. The raw value
in hexadecimal format is not supported by 'send-key' of qmp.
Amos Kong (7):
fix doc of using raw values with sendkey
monitor: rename keyname '<' to 'less'
hmp: rename arguments
qapi: generate list struct and visit_list for enum
qapi: add the QKeyCode enum
monitor: move key_defs[] table and introduce two help functions
qapi: convert sendkey
console.h | 5 +
hmp-commands.hx | 10 +-
hmp.c | 55 +++++++++++
hmp.h | 1 +
input.c | 251 +++++++++++++++++++++++++++++++++++++++++++++++++
monitor.c | 245 +-----------------------------------------------
qapi-schema.json | 46 +++++++++
qmp-commands.hx | 28 ++++++
scripts/qapi-types.py | 16 +++-
scripts/qapi-visit.py | 14 +++-
10 files changed, 421 insertions(+), 250 deletions(-)
---
Changes from v1:
- using a JSON array for the key names
- rename new error to 'QERR_OVERFLOW'
- fix command descriptions
- qapi: generate list struct for enum
- add '<' fixing
Changes from v2:
- fix support of raw value in hexadecimal format
- fix bug in processing of '<-x'
- don't generate useless cleanup functions for enum
- introduced two functions for enum in qapi scripts
- fix command description
- drop keys number limitation in sendkey
- drop patch: qerror: add QERR_OVERFLOW
Changes from v3:
- move key_defs[] to console.h
- link mapping tables by enum values
- rename 'sendkey' to 'send-key' for qmp
Changes from v4:
- rename 'KeyCodes' to 'QKeyCode'
- fix default hold-time
- move qmp_send_key(), key_defs to input.c
- duplicate the keylist in qmp_send_key()
- drop struct KeyDef
- handle invalid key/index in hmp_send_key()
Changes from v5:
- split the addition of the QKeyCode enum and the key_defs table
- split help functions definition
- fix cmd completion and make key_defs static
- drop ps2 trival fix, will post it by another thread
Changes from v6:
- split convert patch to two patches, and do the refactorings
in first patch.
Changes from v7:
- rebase patchset to latest upstream/master
- move the addition of QKeyCode out of patch5
- update version to 1.3.0
next reply other threads:[~2012-08-31 2:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-31 2:56 Amos Kong [this message]
2012-08-31 2:56 ` [Qemu-devel] [PATCH v8 1/7] fix doc of using raw values with sendkey Amos Kong
2012-08-31 2:56 ` [Qemu-devel] [PATCH v8 2/7] monitor: rename keyname '<' to 'less' Amos Kong
2012-08-31 2:56 ` [Qemu-devel] [PATCH v8 3/7] hmp: rename arguments Amos Kong
2012-08-31 2:56 ` [Qemu-devel] [PATCH v8 4/7] qapi: generate list struct and visit_list for enum Amos Kong
2012-08-31 2:56 ` [Qemu-devel] [PATCH v8 5/7] qapi: add the QKeyCode enum Amos Kong
2012-08-31 2:56 ` [Qemu-devel] [PATCH v8 6/7] monitor: move key_defs[] table and introduce two help functions Amos Kong
2012-08-31 2:56 ` [Qemu-devel] [PATCH v8 7/7] qapi: convert sendkey Amos Kong
2012-08-31 14:33 ` [Qemu-devel] [PATCH v8 0/7] convert sendkey to qapi Luiz Capitulino
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=1346381786-18626-1-git-send-email-akong@redhat.com \
--to=akong@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=eblake@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 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.