From: "Benoît Canet" <benoit.canet@irqsave.net>
To: qemu-devel@nongnu.org
Cc: "Benoît Canet" <benoit.canet@irqsave.net>,
wenchaoqemu@gmail.com, armbru@redhat.com, lcapitulino@redhat.com,
anthony@codemonkey.ws
Subject: [Qemu-devel] [PATCH 0/2] Create and include directive for QAPI JSON files
Date: Fri, 21 Mar 2014 17:01:11 +0100 [thread overview]
Message-ID: <1395417673-17710-1-git-send-email-benoit.canet@irqsave.net> (raw)
The first patch make an error path in the test more explicit.
The second create an include directive for QAPI JSON files.
The purpose of this series is to be able to add QMP to qemu-nbd in a not so
distant future.
Best regards
Benoît
Benoît Canet (2):
test-qapi: Make test-qapi.py spit useful error messages.
qapi: Create an include directive for use in the JSON description
files.
Makefile | 24 +++++------
scripts/qapi-commands.py | 8 +++-
scripts/qapi-types.py | 8 +++-
scripts/qapi-visit.py | 8 +++-
scripts/qapi.py | 46 +++++++++++++++++-----
tests/Makefile | 16 ++++----
tests/qapi-schema/duplicate-key.err | 2 +-
.../qapi-schema/flat-union-invalid-branch-key.err | 2 +-
.../flat-union-invalid-discriminator.err | 2 +-
tests/qapi-schema/flat-union-no-base.err | 2 +-
.../flat-union-string-discriminator.err | 2 +-
tests/qapi-schema/funny-char.err | 2 +-
tests/qapi-schema/include.err | 0
tests/qapi-schema/include.exit | 1 +
tests/qapi-schema/include.json | 4 ++
tests/qapi-schema/include.out | 8 ++++
tests/qapi-schema/include/include.json | 7 ++++
tests/qapi-schema/include_loop.err | 0
tests/qapi-schema/include_loop.exit | 1 +
tests/qapi-schema/include_loop.json | 1 +
tests/qapi-schema/include_loop.out | 1 +
tests/qapi-schema/missing-colon.err | 2 +-
tests/qapi-schema/missing-comma-list.err | 2 +-
tests/qapi-schema/missing-comma-object.err | 2 +-
tests/qapi-schema/non-objects.err | 2 +-
tests/qapi-schema/quoted-structural-chars.err | 2 +-
tests/qapi-schema/test-qapi.py | 6 +--
tests/qapi-schema/trailing-comma-list.err | 2 +-
tests/qapi-schema/trailing-comma-object.err | 2 +-
tests/qapi-schema/unclosed-list.err | 2 +-
tests/qapi-schema/unclosed-object.err | 2 +-
tests/qapi-schema/unclosed-string.err | 2 +-
tests/qapi-schema/union-invalid-base.err | 2 +-
33 files changed, 118 insertions(+), 55 deletions(-)
create mode 100644 tests/qapi-schema/include.err
create mode 100644 tests/qapi-schema/include.exit
create mode 100644 tests/qapi-schema/include.json
create mode 100644 tests/qapi-schema/include.out
create mode 100644 tests/qapi-schema/include/include.json
create mode 100644 tests/qapi-schema/include_loop.err
create mode 100644 tests/qapi-schema/include_loop.exit
create mode 100644 tests/qapi-schema/include_loop.json
create mode 100644 tests/qapi-schema/include_loop.out
--
1.8.3.2
next reply other threads:[~2014-03-21 16:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-21 16:01 Benoît Canet [this message]
2014-03-21 16:01 ` [Qemu-devel] [PATCH 1/2] test-qapi: Make test-qapi.py spit useful error messages Benoît Canet
2014-03-27 2:47 ` Eric Blake
2014-03-21 16:01 ` [Qemu-devel] [PATCH 2/2] qapi: Create an include directive for use in the JSON description files Benoît Canet
2014-03-27 1:49 ` Wenchao Xia
2014-03-27 2:58 ` Eric Blake
2014-03-27 2:58 ` Eric Blake
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=1395417673-17710-1-git-send-email-benoit.canet@irqsave.net \
--to=benoit.canet@irqsave.net \
--cc=anthony@codemonkey.ws \
--cc=armbru@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=wenchaoqemu@gmail.com \
/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.