From: John Snow <jsnow@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Zhao Liu" <zhao1.liu@intel.com>,
"Igor Mammedov" <imammedo@redhat.com>,
"Vladimir Sementsov-Ogievskiy" <vsementsov@yandex-team.ru>,
"Jason Wang" <jasowangio@gmail.com>,
"Eric Blake" <eblake@redhat.com>,
"Markus Armbruster" <armbru@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Hanna Reitz" <hreitz@redhat.com>,
"Ani Sinha" <anisinha@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Fabiano Rosas" <farosas@suse.de>, "Peter Xu" <peterx@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@oss.qualcomm.com>,
"Kevin Wolf" <kwolf@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
qemu-block@nongnu.org, "John Snow" <jsnow@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@mailo.com>
Subject: [PATCH v3 05/10] qapi: convert/split intros for misc-i386.json commands
Date: Mon, 28 Sep 2026 15:25:52 -0400 [thread overview]
Message-ID: <20260928192557.509157-6-jsnow@redhat.com> (raw)
In-Reply-To: <20260928192557.509157-1-jsnow@redhat.com>
Convert or split apart the existing intro for commands in
misc-i386.json into introduction and details sections. The
introduction is indented, remaining plaintext/details paragraphs are
not.
For commands that have automatically generated documentation inserted
at parse time, these new split points serve as the new insertion
point. This affects the rendered documentation for `query-sev` in
particular, whose "Returns:" documentation is pushed upwards.
Signed-off-by: John Snow <jsnow@redhat.com>
---
qapi/misc-i386.json | 22 ++++++++--------------
1 file changed, 8 insertions(+), 14 deletions(-)
diff --git a/qapi/misc-i386.json b/qapi/misc-i386.json
index 78ec9aec647..6e0ab46b8ea 100644
--- a/qapi/misc-i386.json
+++ b/qapi/misc-i386.json
@@ -5,10 +5,9 @@
##
# @rtc-reset-reinjection:
-#
-# Reset the RTC interrupt reinjection backlog. Can be used if another
-# mechanism to synchronize guest time is in effect, for example QEMU
-# guest agent's `guest-set-time` command.
+# Reset the RTC interrupt reinjection backlog. Can be used if
+# another mechanism to synchronize guest time is in effect, for
+# example QEMU guest agent's `guest-set-time` command.
#
# Use of this command is only applicable for x86 machines with an RTC,
# and on other machines will silently return without performing any
@@ -119,8 +118,7 @@
##
# @query-sev:
-#
-# Return information about SEV/SEV-ES/SEV-SNP.
+# Return information about SEV/SEV-ES/SEV-SNP.
#
# If unavailable due to an incompatible configuration the returned
# @enabled field is set to 'false' and the state of all other fields
@@ -149,8 +147,7 @@
##
# @query-sev-launch-measure:
-#
-# Query the SEV/SEV-ES guest launch information.
+# Query the SEV/SEV-ES guest launch information.
#
# This is only valid on x86 machines configured with KVM and the
# 'sev-guest' confidential virtualization object. The launch
@@ -199,8 +196,7 @@
##
# @query-sev-capabilities:
-#
-# Get SEV capabilities.
+# Get SEV capabilities.
#
# This is only supported on AMD X86 platforms with KVM enabled.
#
@@ -220,8 +216,7 @@
##
# @sev-inject-launch-secret:
-#
-# Inject a secret blob into a SEV/SEV-ES guest's memory.
+# Inject a secret blob into a SEV/SEV-ES guest's memory.
#
# This is only valid on x86 machines configured with KVM and the
# 'sev-guest' confidential virtualization object. SEV-SNP guests do
@@ -257,8 +252,7 @@
##
# @query-sev-attestation-report:
-#
-# Get the SEV attestation report.
+# Get the SEV attestation report.
#
# This is only valid on x86 machines configured with KVM and the
# 'sev-guest' confidential virtualization object. The attestation
--
2.55.0
next prev parent reply other threads:[~2026-09-28 19:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 19:25 [PATCH v3 00/10] qapi: convert/split remaining QAPI/QMP intro sections John Snow
2026-09-28 19:25 ` [PATCH v3 01/10] qapi: split intro for HV_BALLOON_STATUS_REPORT John Snow
2026-09-28 19:25 ` [PATCH v3 02/10] qapi: convert/split intros for block-core.json commands John Snow
2026-09-29 6:00 ` Markus Armbruster
2026-09-29 14:58 ` John Snow
2026-09-28 19:25 ` [PATCH v3 03/10] qapi: convert/split intros for block commands John Snow
2026-09-29 6:17 ` Markus Armbruster
2026-09-29 14:59 ` John Snow
2026-09-28 19:25 ` [PATCH v3 04/10] qapi: convert/split intros for job.json commands John Snow
2026-09-28 19:25 ` John Snow [this message]
2026-09-28 19:25 ` [PATCH v3 06/10] qapi: convert/split intros for commands John Snow
2026-09-29 6:22 ` Markus Armbruster
2026-09-29 15:03 ` John Snow
2026-09-28 19:25 ` [PATCH v3 07/10] qapi: convert/split intros for enums John Snow
2026-09-28 19:25 ` [PATCH v3 08/10] qapi: split intro sections for events John Snow
2026-09-28 19:25 ` [PATCH v3 09/10] qapi: split intro sections for data structs John Snow
2026-09-28 19:25 ` [PATCH v3 10/10] qapi: split intro sections for inlinable structs John Snow
2026-09-29 6:24 ` Markus Armbruster
2026-09-29 15:03 ` John Snow
2026-09-29 6:32 ` [PATCH v3 00/10] qapi: convert/split remaining QAPI/QMP intro sections 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=20260928192557.509157-6-jsnow@redhat.com \
--to=jsnow@redhat.com \
--cc=anisinha@redhat.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=eblake@redhat.com \
--cc=farosas@suse.de \
--cc=hreitz@redhat.com \
--cc=imammedo@redhat.com \
--cc=jasowangio@gmail.com \
--cc=kwolf@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=philmd@mailo.com \
--cc=philmd@oss.qualcomm.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@yandex-team.ru \
--cc=zhao1.liu@intel.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.