From: John Snow <jsnow@redhat.com>
To: qemu-devel@nongnu.org
Cc: qemu-block@nongnu.org, "Kevin Wolf" <kwolf@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@mailo.com>,
"Eric Blake" <eblake@redhat.com>,
"Jonathan Cameron" <jic23@kernel.org>,
"Lukas Straub" <lukasstraub2@web.de>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Zhao Liu" <zhao1.liu@intel.com>,
linux-cxl@vger.kernel.org, "Jason Wang" <jasowangio@gmail.com>,
"Hanna Reitz" <hreitz@redhat.com>,
"Markus Armbruster" <armbru@redhat.com>,
"Fabiano Rosas" <farosas@suse.de>, "Peter Xu" <peterx@redhat.com>,
"John Snow" <jsnow@redhat.com>
Subject: [PATCH 4/6] qapi: convert remaining simple intros for block-core.json
Date: Fri, 11 Sep 2026 13:21:58 -0400 [thread overview]
Message-ID: <20260911172200.227914-5-jsnow@redhat.com> (raw)
In-Reply-To: <20260911172200.227914-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-core.json | 45 +++++++++++++++++++-------------------------
1 file changed, 19 insertions(+), 26 deletions(-)
diff --git a/qapi/block-core.json b/qapi/block-core.json
index 1ca147285e7..88218e38d02 100644
--- a/qapi/block-core.json
+++ b/qapi/block-core.json
@@ -4462,9 +4462,8 @@
##
# @BlockdevOptionsCurlHttp:
-#
-# Driver specific block device options for HTTP connections over the
-# curl backend. URLs must start with "http://".
+# Driver specific block device options for HTTP connections over
+# the curl backend. URLs must start with "http://".
#
# @cookie: List of cookies to set; format is "name1=content1;
# name2=content2;" as explained by CURLOPT_COOKIE(3). Defaults to
@@ -4488,9 +4487,8 @@
##
# @BlockdevOptionsCurlHttps:
-#
-# Driver specific block device options for HTTPS connections over the
-# curl backend. URLs must start with "https://".
+# Driver specific block device options for HTTPS connections over
+# the curl backend. URLs must start with "https://".
#
# @sslverify: Whether to verify the SSL certificate's validity
# (defaults to true)
@@ -4503,9 +4501,8 @@
##
# @BlockdevOptionsCurlFtp:
-#
-# Driver specific block device options for FTP connections over the
-# curl backend. URLs must start with "ftp://".
+# Driver specific block device options for FTP connections over
+# the curl backend. URLs must start with "ftp://".
#
# Since: 2.9
##
@@ -4515,9 +4512,8 @@
##
# @BlockdevOptionsCurlFtps:
-#
-# Driver specific block device options for FTPS connections over the
-# curl backend. URLs must start with "ftps://".
+# Driver specific block device options for FTPS connections over
+# the curl backend. URLs must start with "ftps://".
#
# @sslverify: Whether to verify the SSL certificate's validity
# (defaults to true)
@@ -4643,14 +4639,13 @@
##
# @BlockdevOptionsCbw:
-#
-# Driver specific block device options for the copy-before-write
-# driver, which does so called copy-before-write operations: when data
-# is written to the filter, the filter first reads corresponding
-# blocks from its file child and copies them to @target child. After
-# successfully copying, the write request is propagated to file child.
-# If copying fails, the original write request is failed too and no
-# data is written to file child.
+# Driver specific block device options for the copy-before-write
+# driver, which does so called copy-before-write operations: when
+# data is written to the filter, the filter first reads
+# corresponding blocks from its file child and copies them to
+# @target child. After successfully copying, the write request is
+# propagated to file child. If copying fails, the original write
+# request is failed too and no data is written to file child.
#
# @target: The target for copy-before-write operations.
#
@@ -4686,9 +4681,8 @@
##
# @BlockdevOptions:
-#
-# Options for creating a block device. Many options are available for
-# all block devices, independent of the block driver:
+# Options for creating a block device. Many options are available
+# for all block devices, independent of the block driver:
#
# @driver: block driver name
#
@@ -5473,9 +5467,8 @@
##
# @BlockdevAmendOptionsQcow2:
-#
-# Driver specific image amend options for qcow2. For now, only
-# encryption options can be amended
+# Driver specific image amend options for qcow2. For now, only
+# encryption options can be amended
#
# @encrypt: Encryption options to be amended
#
--
2.55.0
next prev parent reply other threads:[~2026-09-11 17:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-11 17:21 [PATCH 0/6] qapi: convert remaining "simple" intro sections John Snow
2026-09-11 17:21 ` [PATCH 1/6] qapi: convert remaining simple intros for block-export.json John Snow
2026-09-12 7:34 ` Markus Armbruster
2026-09-11 17:21 ` [PATCH 2/6] qapi: convert remaining simple intros for cxl.json John Snow
2026-09-11 17:21 ` [PATCH 3/6] qapi: convert remaining simple intros for machine.json John Snow
2026-09-12 7:34 ` Markus Armbruster
2026-09-11 17:21 ` John Snow [this message]
2026-09-12 7:35 ` [PATCH 4/6] qapi: convert remaining simple intros for block-core.json Markus Armbruster
2026-09-11 17:21 ` [PATCH 5/6] qapi: convert intro sections with "TODO" markers John Snow
2026-09-12 6:58 ` Markus Armbruster
2026-09-11 17:22 ` [PATCH 6/6] qapi: convert intro sections followed by notes/examples John Snow
2026-09-12 7:36 ` [PATCH 0/6] qapi: convert remaining "simple" 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=20260911172200.227914-5-jsnow@redhat.com \
--to=jsnow@redhat.com \
--cc=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=farosas@suse.de \
--cc=hreitz@redhat.com \
--cc=jasowangio@gmail.com \
--cc=jic23@kernel.org \
--cc=kwolf@redhat.com \
--cc=linux-cxl@vger.kernel.org \
--cc=lukasstraub2@web.de \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=philmd@mailo.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox