From: Markus Armbruster <armbru@redhat.com>
To: qemu-devel@nongnu.org
Cc: eblake@redhat.com, mlureau@redhat.com
Subject: [Qemu-devel] [PATCH 0/4] qapi: Handle some keyval fallout
Date: Mon, 22 May 2017 18:42:11 +0200 [thread overview]
Message-ID: <1495471335-23707-1-git-send-email-armbru@redhat.com> (raw)
Markus Armbruster (4):
qobject-input-visitor: Reject non-finite numbers with keyval
qapi: Document visit_type_any() issues with keyval input
tests/qapi-schema: Avoid 'str' in alternate test cases
qapi: Reject alternates that can't work with keyval_parse()
include/qapi/visitor.h | 4 ++
qapi/qobject-input-visitor.c | 3 +-
scripts/qapi.py | 19 ++++++-
tests/Makefile.include | 2 +
tests/qapi-schema/alternate-clash.json | 2 +-
tests/qapi-schema/alternate-conflict-dict.json | 2 +-
tests/qapi-schema/alternate-conflict-enum-bool.err | 1 +
.../qapi-schema/alternate-conflict-enum-bool.exit | 1 +
.../qapi-schema/alternate-conflict-enum-bool.json | 6 +++
tests/qapi-schema/alternate-conflict-enum-bool.out | 0
tests/qapi-schema/alternate-conflict-enum-int.err | 1 +
tests/qapi-schema/alternate-conflict-enum-int.exit | 1 +
tests/qapi-schema/alternate-conflict-enum-int.json | 6 +++
tests/qapi-schema/alternate-conflict-enum-int.out | 0
tests/qapi-schema/alternate-conflict-string.err | 2 +-
tests/qapi-schema/alternate-conflict-string.json | 6 +--
tests/qapi-schema/alternate-nested.json | 2 +-
tests/qapi-schema/args-alternate.json | 2 +-
tests/qapi-schema/doc-bad-alternate-member.json | 2 +-
tests/qapi-schema/qapi-schema-test.json | 13 +++--
tests/qapi-schema/qapi-schema-test.out | 34 ++++++------
tests/qapi-schema/returns-alternate.json | 2 +-
tests/test-clone-visitor.c | 23 ++++----
tests/test-keyval.c | 18 ++++---
tests/test-qobject-input-visitor.c | 62 ++++++++++++----------
tests/test-qobject-output-visitor.c | 4 +-
util/keyval.c | 10 ++--
27 files changed, 140 insertions(+), 88 deletions(-)
create mode 100644 tests/qapi-schema/alternate-conflict-enum-bool.err
create mode 100644 tests/qapi-schema/alternate-conflict-enum-bool.exit
create mode 100644 tests/qapi-schema/alternate-conflict-enum-bool.json
create mode 100644 tests/qapi-schema/alternate-conflict-enum-bool.out
create mode 100644 tests/qapi-schema/alternate-conflict-enum-int.err
create mode 100644 tests/qapi-schema/alternate-conflict-enum-int.exit
create mode 100644 tests/qapi-schema/alternate-conflict-enum-int.json
create mode 100644 tests/qapi-schema/alternate-conflict-enum-int.out
--
2.7.4
next reply other threads:[~2017-05-22 16:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-22 16:42 Markus Armbruster [this message]
2017-05-22 16:42 ` [Qemu-devel] [PATCH 1/4] qobject-input-visitor: Reject non-finite numbers with keyval Markus Armbruster
2017-05-22 17:46 ` Eric Blake
2017-05-22 16:42 ` [Qemu-devel] [PATCH 2/4] qapi: Document visit_type_any() issues with keyval input Markus Armbruster
2017-05-22 17:47 ` Eric Blake
2017-05-22 16:42 ` [Qemu-devel] [PATCH 3/4] tests/qapi-schema: Avoid 'str' in alternate test cases Markus Armbruster
2017-05-22 17:55 ` Eric Blake
2017-05-22 16:42 ` [Qemu-devel] [PATCH 4/4] qapi: Reject alternates that can't work with keyval_parse() Markus Armbruster
2017-05-22 18:18 ` Eric Blake
2017-05-23 8:45 ` Markus Armbruster
2017-05-26 10:30 ` [Qemu-devel] [PATCH 0/4] qapi: Handle some keyval fallout Marc-André Lureau
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=1495471335-23707-1-git-send-email-armbru@redhat.com \
--to=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=mlureau@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).