All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Snow <jsnow@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Laurent Vivier" <laurent@vivier.eu>,
	"Kostiantyn Kostiuk" <kkostiuk@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	"Zhao Liu" <zhao1.liu@intel.com>,
	"Michael Roth" <michael.roth@amd.com>,
	"Pierrick Bouvier" <pierrick.bouvier@oss.qualcomm.com>,
	"Daniel P. Berrangé" <berrange@redhat.com>,
	"Jason Wang" <jasowangio@gmail.com>,
	qemu-trivial@nongnu.org,
	"Philippe Mathieu-Daudé" <philmd@oss.qualcomm.com>,
	"Stefano Garzarella" <sgarzare@redhat.com>,
	"Kashyap Chamarthy" <kchamart@redhat.com>,
	"Eric Blake" <eblake@redhat.com>,
	"Hanna Reitz" <hreitz@redhat.com>,
	"Markus Armbruster" <armbru@redhat.com>,
	"Kevin Wolf" <kwolf@redhat.com>,
	qemu-block@nongnu.org, "Michael Tokarev" <mjt@tls.msk.ru>,
	"John Snow" <jsnow@redhat.com>
Subject: [PATCH v2 5/8] qapi: split intros at natural cutoff points for qga/qapi-schema.json
Date: Tue, 22 Sep 2026 16:56:02 -0400	[thread overview]
Message-ID: <20260922205605.501602-6-jsnow@redhat.com> (raw)
In-Reply-To: <20260922205605.501602-1-jsnow@redhat.com>

Note that these intro conversions introduce a new intro/details split
point. This new split point may or may not change the rendered output
depending on if any documentation is auto-generated and inserted for
this definition.

This has tangible effects on how @guest-fsfreeze-status documentation
is rendered, while the other two appear unchanged.

Signed-off-by: John Snow <jsnow@redhat.com>
---
 qga/qapi-schema.json | 11 ++++-------
 1 file changed, 4 insertions(+), 7 deletions(-)

diff --git a/qga/qapi-schema.json b/qga/qapi-schema.json
index b592b14a011..19b0958b84e 100644
--- a/qga/qapi-schema.json
+++ b/qga/qapi-schema.json
@@ -401,8 +401,7 @@
 
 ##
 # @guest-fsfreeze-status:
-#
-# Get guest fsfreeze state.
+#     Get guest fsfreeze state.
 #
 # .. note:: This may fail to properly report the current state as a
 #    result of some other guest processes having issued an fs
@@ -925,9 +924,8 @@
 
 ##
 # @GuestNVMeSmart:
-#
-# NVMe smart information, based on NVMe specification, section
-# <SMART / Health Information (Log Identifier 02h)>
+#     NVMe smart information, based on NVMe specification, section
+#     <SMART / Health Information (Log Identifier 02h)>
 #
 # TODO: document members briefly
 #
@@ -1816,8 +1814,7 @@
 
 ##
 # @guest-get-load:
-#
-# Retrieve CPU process load information
+#     Retrieve CPU process load information
 #
 # .. note:: Windows does not have load average API, so QGA emulates it
 #    by calculating the average CPU usage in the last 1, 5, 15 minutes
-- 
2.55.0



  parent reply	other threads:[~2026-09-22 20:58 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-22 20:55 [PATCH v2 0/8] qapi: convert intros for qga, firmware, etc John Snow
2026-09-22 20:55 ` [PATCH v2 1/8] qapi: convert/split remaining qapi/qmp intro sections John Snow
2026-09-22 20:55 ` [PATCH v2 2/8] qapi: convert intro sections for unit tests John Snow
2026-09-23  6:07   ` Markus Armbruster
2026-09-23 17:17     ` John Snow
2026-09-22 20:56 ` [PATCH v2 3/8] qapi: convert trivial intros for qga/qapi-schema.json John Snow
2026-09-22 20:56 ` [PATCH v2 4/8] qapi: convert simple " John Snow
2026-09-22 20:56 ` John Snow [this message]
2026-09-23  6:25   ` [PATCH v2 5/8] qapi: split intros at natural cutoff points " Markus Armbruster
2026-09-23 17:18     ` John Snow
2026-09-22 20:56 ` [PATCH v2 6/8] qapi: split intros " John Snow
2026-09-22 20:56 ` [PATCH v2 7/8] qapi: convert intro sections for docs/interop/firmware.json John Snow
2026-09-22 20:56 ` [PATCH v2 8/8] qapi: convert intro sections for docs/interop/vhost-user.json John Snow
2026-09-23  6:45 ` [PATCH v2 0/8] qapi: convert intros for qga, firmware, etc Markus Armbruster
2026-09-23  6:49   ` Markus Armbruster
2026-09-23 17:19     ` John Snow

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=20260922205605.501602-6-jsnow@redhat.com \
    --to=jsnow@redhat.com \
    --cc=armbru@redhat.com \
    --cc=berrange@redhat.com \
    --cc=eblake@redhat.com \
    --cc=hreitz@redhat.com \
    --cc=jasowangio@gmail.com \
    --cc=kchamart@redhat.com \
    --cc=kkostiuk@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=laurent@vivier.eu \
    --cc=michael.roth@amd.com \
    --cc=mjt@tls.msk.ru \
    --cc=mst@redhat.com \
    --cc=philmd@oss.qualcomm.com \
    --cc=pierrick.bouvier@oss.qualcomm.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@nongnu.org \
    --cc=sgarzare@redhat.com \
    --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.