From: Markus Armbruster <armbru@redhat.com>
To: qemu-devel@nongnu.org
Cc: stefanha@redhat.com
Subject: [PULL 0/6] QAPI patches patches for 2025-02-10
Date: Mon, 10 Feb 2025 09:39:40 +0100 [thread overview]
Message-ID: <20250210083946.3553415-1-armbru@redhat.com> (raw)
The following changes since commit 04d3d0e9f54d4c42759f3810aa135ce314d98dc4:
Merge tag 'hppa-system-for-v10-diva-artist-pull-request' of https://github.com/hdeller/qemu-hppa into staging (2025-02-08 09:00:57 -0500)
are available in the Git repository at:
https://repo.or.cz/qemu/armbru.git tags/pull-qapi-2025-02-10
for you to fetch changes up to 9c339601b652edf91d74a626999285e3245b2589:
qapi: expose all schema features to code (2025-02-10 09:14:14 +0100)
----------------------------------------------------------------
QAPI patches patches for 2025-02-10
----------------------------------------------------------------
Daniel P. Berrangé (4):
qapi: cope with feature names containing a '-'
qapi: change 'unsigned special_features' to 'uint64_t features'
qapi: rename 'special_features' to 'features'
qapi: expose all schema features to code
Victor Toso (1):
qapi: fix colon in Since tag section
Zhang Boyang (1):
qapi/ui: Fix documentation of upper bound value in InputMoveEvent
meson.build | 1 +
qapi/cxl.json | 4 +--
qapi/ui.json | 2 +-
include/qapi/compat-policy.h | 2 +-
include/qapi/qmp/dispatch.h | 4 +--
include/qapi/util.h | 2 +-
include/qapi/visitor-impl.h | 4 +--
include/qapi/visitor.h | 12 ++++----
qapi/qapi-forward-visitor.c | 8 +++---
qapi/qapi-util.c | 6 ++--
qapi/qapi-visit-core.c | 12 ++++----
qapi/qmp-dispatch.c | 2 +-
qapi/qmp-registry.c | 4 +--
qapi/qobject-input-visitor.c | 4 +--
qapi/qobject-output-visitor.c | 6 ++--
scripts/qapi/commands.py | 5 ++--
scripts/qapi/features.py | 48 ++++++++++++++++++++++++++++++++
scripts/qapi/gen.py | 9 +++---
scripts/qapi/main.py | 2 ++
scripts/qapi/schema.py | 31 ++++++++++++++++++++-
scripts/qapi/types.py | 23 ++++++++-------
scripts/qapi/visit.py | 21 ++++++--------
tests/meson.build | 2 ++
tests/qapi-schema/features-too-many.err | 2 ++
tests/qapi-schema/features-too-many.json | 13 +++++++++
tests/qapi-schema/features-too-many.out | 0
tests/qapi-schema/meson.build | 1 +
27 files changed, 163 insertions(+), 67 deletions(-)
create mode 100644 scripts/qapi/features.py
create mode 100644 tests/qapi-schema/features-too-many.err
create mode 100644 tests/qapi-schema/features-too-many.json
create mode 100644 tests/qapi-schema/features-too-many.out
--
2.48.1
next reply other threads:[~2025-02-10 8:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-10 8:39 Markus Armbruster [this message]
2025-02-10 8:39 ` [PULL 1/6] qapi: fix colon in Since tag section Markus Armbruster
2025-02-10 8:39 ` [PULL 2/6] qapi/ui: Fix documentation of upper bound value in InputMoveEvent Markus Armbruster
2025-02-10 8:39 ` [PULL 3/6] qapi: cope with feature names containing a '-' Markus Armbruster
2025-02-10 8:39 ` [PULL 4/6] qapi: change 'unsigned special_features' to 'uint64_t features' Markus Armbruster
2025-02-10 8:39 ` [PULL 5/6] qapi: rename 'special_features' to 'features' Markus Armbruster
2025-02-10 8:39 ` [PULL 6/6] qapi: expose all schema features to code Markus Armbruster
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=20250210083946.3553415-1-armbru@redhat.com \
--to=armbru@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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 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).