From: John Snow <jsnow@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Zhao Liu" <zhao1.liu@intel.com>,
"Jason Wang" <jasowangio@gmail.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Fabiano Rosas" <farosas@suse.de>,
"Philippe Mathieu-Daudé" <philmd@mailo.com>,
"Hanna Reitz" <hreitz@redhat.com>,
"Kevin Wolf" <kwolf@redhat.com>,
"Markus Armbruster" <armbru@redhat.com>,
"Vladimir Sementsov-Ogievskiy" <vsementsov@yandex-team.ru>,
qemu-block@nongnu.org, "John Snow" <jsnow@redhat.com>,
"Eric Blake" <eblake@redhat.com>,
"Igor Mammedov" <imammedo@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Peter Xu" <peterx@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Ani Sinha" <anisinha@redhat.com>
Subject: [PATCH 1/9] qapi: convert remaining simple intros for block-export.json
Date: Fri, 11 Sep 2026 16:29:54 -0400 [thread overview]
Message-ID: <20260911203002.305316-2-jsnow@redhat.com> (raw)
In-Reply-To: <20260911203002.305316-1-jsnow@redhat.com>
These are either structs or unions that are used in an inlinable
context: i.e. the generated documentation is likely to feature a
version of this documentation block that does not include the intro in
context of another command, event, or structure.
Signed-off-by: John Snow <jsnow@redhat.com>
---
qapi/block-export.json | 19 ++++++++-----------
1 file changed, 8 insertions(+), 11 deletions(-)
diff --git a/qapi/block-export.json b/qapi/block-export.json
index 2893c6456d5..e9f7e72c8ee 100644
--- a/qapi/block-export.json
+++ b/qapi/block-export.json
@@ -37,10 +37,9 @@
##
# @NbdServerOptions:
-#
-# Keep this type consistent with the `NbdServerOptionsLegacy` type.
-# The only intended difference is using `SocketAddress` instead of
-# `SocketAddressLegacy`.
+# Keep this type consistent with the `NbdServerOptionsLegacy`
+# type. The only intended difference is using `SocketAddress`
+# instead of `SocketAddressLegacy`.
#
# @addr: Address on which to listen (since 4.2).
##
@@ -50,10 +49,9 @@
##
# @NbdServerOptionsLegacy:
-#
-# Keep this type consistent with the `NbdServerOptions` type. The
-# only intended difference is using `SocketAddressLegacy` instead of
-# `SocketAddress`.
+# Keep this type consistent with the `NbdServerOptions` type. The
+# only intended difference is using `SocketAddressLegacy` instead
+# of `SocketAddress`.
#
# @addr: Address on which to listen (since 1.3).
##
@@ -339,9 +337,8 @@
##
# @BlockExportOptions:
-#
-# Describes a block export, i.e. how single node should be exported on
-# an external interface.
+# Describes a block export, i.e. how single node should be
+# exported on an external interface.
#
# @type: Block export type
#
--
2.55.0
next prev parent reply other threads:[~2026-09-11 20:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-11 20:29 [PATCH 0/9] qapi: convert/split remaining QAPI/QMP intro sections John Snow
2026-09-11 20:29 ` John Snow [this message]
2026-09-12 7:02 ` [PATCH 1/9] qapi: convert remaining simple intros for block-export.json Markus Armbruster
2026-09-11 20:29 ` [PATCH 2/9] qapi: convert multi-paragraph intros (commands) John Snow
2026-09-11 20:29 ` [PATCH 3/9] qapi: convert multi-paragraph intros (enums) John Snow
2026-09-11 20:29 ` [PATCH 4/9] qapi: convert multi-paragraph intros (structs) John Snow
2026-09-11 20:29 ` [PATCH 5/9] qapi: split intro sections for commands John Snow
2026-09-11 20:29 ` [PATCH 6/9] qapi: split intro sections for events John Snow
2026-09-11 20:30 ` [PATCH 7/9] qapi: split intro sections for enums John Snow
2026-09-11 20:30 ` [PATCH 8/9] qapi: split intro sections for data structs John Snow
2026-09-11 20:30 ` [PATCH 9/9] qapi: split intro sections for inlinable structs 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=20260911203002.305316-2-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=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.