All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: John Snow <jsnow@redhat.com>
Cc: qemu-devel@nongnu.org,
	"Marc-André Lureau" <marcandre.lureau@redhat.com>,
	"Fabiano Rosas" <farosas@suse.de>,
	"Hanna Reitz" <hreitz@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@mailo.com>,
	"Kevin Wolf" <kwolf@redhat.com>,
	"Vladimir Sementsov-Ogievskiy" <vsementsov@yandex-team.ru>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Zhao Liu" <zhao1.liu@intel.com>,
	"Jason Wang" <jasowangio@gmail.com>,
	"Eric Blake" <eblake@redhat.com>,
	qemu-block@nongnu.org, "Igor Mammedov" <imammedo@redhat.com>,
	"Ani Sinha" <anisinha@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	"Peter Xu" <peterx@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@oss.qualcomm.com>,
	"Daniel P. Berrangé" <berrange@redhat.com>
Subject: Re: [PATCH v2 10/10] qapi: split intro sections for inlinable structs
Date: Wed, 23 Sep 2026 11:59:30 +0200	[thread overview]
Message-ID: <87se30uw3h.fsf@pond.sub.org> (raw)
In-Reply-To: <20260921205712.1862167-11-jsnow@redhat.com> (John Snow's message of "Mon, 21 Sep 2026 16:57:12 -0400")

John Snow <jsnow@redhat.com> writes:

> This patch splits the intro/details section for structs which are used
> in an inlinable context; i.e. structs used either as arguments for a
> command/event, or used as a branch of a union. The QAPI documentation
> block for these entities will have their "intro" section removed when
> inlined into other contexts, but may still display the intro section
> on generated documentation *IF* these structs are also used as an
> argument or return type.
>
> Signed-off-by: John Snow <jsnow@redhat.com>

Consider mentioning how this affects rendered documentation now:
MemoryBackendShmProperties and MemoryBackendEpcProperties member
descriptions move up some.

> ---
>  qapi/block-export.json |  5 ++---
>  qapi/crypto.json       |  3 +--
>  qapi/machine.json      | 11 ++++-------
>  qapi/net.json          | 34 +++++++++++++++-------------------
>  qapi/qom.json          |  9 +++------
>  5 files changed, 25 insertions(+), 37 deletions(-)
>
> diff --git a/qapi/block-export.json b/qapi/block-export.json
> index 77459f6321b..e3cee2fb5ce 100644
> --- a/qapi/block-export.json
> +++ b/qapi/block-export.json
> @@ -154,9 +154,8 @@
>  
>  ##
>  # @BlockExportOptionsFuse:
> -#
> -# Options for exporting a block graph node on some (file) mountpoint
> -# as a raw image.
> +#     Options for exporting a block graph node on some (file)
> +#     mountpoint as a raw image.
>  #
>  # Multi-threading note: The FUSE export supports multi-threading.
>  # Currently, requests are distributed across these threads in a
> diff --git a/qapi/crypto.json b/qapi/crypto.json
> index 7b4c80edae2..a8d753d360f 100644
> --- a/qapi/crypto.json
> +++ b/qapi/crypto.json
> @@ -429,8 +429,7 @@
>  
>  ##
>  # @SecretProperties:
> -#
> -# Properties for secret objects.
> +#     Properties for secret objects.
>  #
>  # Either @data or @file must be provided, but not both.
>  #
> diff --git a/qapi/machine.json b/qapi/machine.json
> index b18c6d94a38..1220116bf7d 100644
> --- a/qapi/machine.json
> +++ b/qapi/machine.json
> @@ -684,9 +684,8 @@
>  
>  ##
>  # @NumaHmatLBOptions:
> -#
> -# Set the system locality latency and bandwidth information between
> -# Initiator and Target proximity Domains.
> +#     Set the system locality latency and bandwidth information
> +#     between Initiator and Target proximity Domains.
>  #
>  # For more information about `NumaHmatLBOptions`, see chapter
>  # 5.2.27.4: Table 5-146 of ACPI 6.3 spec.
> @@ -760,8 +759,7 @@
>  
>  ##
>  # @NumaHmatCacheOptions:
> -#
> -# Set the memory side cache information for a given memory domain.
> +#     Set the memory side cache information for a given memory domain.
>  #
>  # For more information of `NumaHmatCacheOptions`, see chapter
>  # 5.2.27.5: Table 5-147: Field "Cache Attributes" of ACPI 6.3 spec.
> @@ -926,8 +924,7 @@
>  
>  ##
>  # @CpuInstanceProperties:
> -#
> -# Properties identifying a CPU.
> +#     Properties identifying a CPU.
>  #
>  # Which members are optional and which mandatory depends on the
>  # architecture and board.
> diff --git a/qapi/net.json b/qapi/net.json
> index b0a15fd53e2..2a186a71b93 100644
> --- a/qapi/net.json
> +++ b/qapi/net.json
> @@ -719,11 +719,10 @@
>  
>  ##
>  # @NetdevVhostVDPAOptions:
> +#     Vhost-vdpa network backend
>  #
> -# Vhost-vdpa network backend
> -#
> -# vDPA device is a device that uses a datapath which complies with the
> -# virtio specifications with a vendor specific control path.
> +#     vDPA device is a device that uses a datapath which complies with
> +#     the virtio specifications with a vendor specific control path.
>  #

This is an instructive example of a "split or keep in intro" decision
guided by contents: the second paragraph will likely not be useful when
inlined into Netdev, so you keep it in intro.

If the contents of the paragraph would be missed when the inliner elides
it, we'll need to figure out where to put it.  Not now.

>  # @vhostdev: path of vhost-vdpa device (default:'/dev/vhost-vdpa-0')
>  #
> @@ -750,11 +749,10 @@
>  
>  ##
>  # @NetdevVmnetHostOptions:
> +#     vmnet (host mode) network backend.
>  #
> -# vmnet (host mode) network backend.
> -#
> -# Allows the vmnet interface to communicate with other vmnet
> -# interfaces that are in host mode and also with the host.
> +#     Allows the vmnet interface to communicate with other vmnet
> +#     interfaces that are in host mode and also with the host.

Similar.

>  #
>  # @start-address: The starting IPv4 address to use for the interface.
>  #     Must be in the private IP range (RFC 1918).  Must be specified
> @@ -793,15 +791,14 @@
>  
>  ##
>  # @NetdevVmnetSharedOptions:
> +#     vmnet (shared mode) network backend.
>  #
> -# vmnet (shared mode) network backend.
> -#
> -# Allows traffic originating from the vmnet interface to reach the
> -# Internet through a network address translator (NAT).  The vmnet
> -# interface can communicate with the host and with other shared mode
> -# interfaces on the same subnet.  If no DHCP settings, subnet mask and
> -# IPv6 prefix specified, the interface can communicate with any of
> -# other interfaces in shared mode.
> +#     Allows traffic originating from the vmnet interface to reach the
> +#     Internet through a network address translator (NAT).  The vmnet
> +#     interface can communicate with the host and with other shared
> +#     mode interfaces on the same subnet.  If no DHCP settings, subnet
> +#     mask and IPv6 prefix specified, the interface can communicate
> +#     with any of other interfaces in shared mode.

Similar.

>  #
>  # @start-address: The starting IPv4 address to use for the interface.
>  #     Must be in the private IP range (RFC 1918).  Must be specified
> @@ -838,10 +835,9 @@
>  
>  ##
>  # @NetdevVmnetBridgedOptions:
> +#     vmnet (bridged mode) network backend.
>  #
> -# vmnet (bridged mode) network backend.
> -#
> -# Bridges the vmnet interface with a physical network interface.
> +#     Bridges the vmnet interface with a physical network interface.

Similar.

>  #
>  # @ifname: The name of the physical interface to be bridged.
>  #
> diff --git a/qapi/qom.json b/qapi/qom.json
> index 51af9485e6d..e67cd0cd54d 100644
> --- a/qapi/qom.json
> +++ b/qapi/qom.json
> @@ -456,8 +456,7 @@
>  
>  ##
>  # @FilterRedirectorProperties:
> -#
> -# Properties for filter-redirector objects.
> +#     Properties for filter-redirector objects.
>  #
>  # At least one of @indev or @outdev must be present.  If both are
>  # present, they must not refer to the same character device backend.
> @@ -756,8 +755,7 @@
>  
>  ##
>  # @MemoryBackendShmProperties:
> -#
> -# Properties for memory-backend-shm objects.
> +#     Properties for memory-backend-shm objects.
>  #
>  # This memory backend supports only shared memory, which is the
>  # default.
> @@ -771,8 +769,7 @@
>  
>  ##
>  # @MemoryBackendEpcProperties:
> -#
> -# Properties for memory-backend-epc objects.
> +#     Properties for memory-backend-epc objects.
>  #
>  # The @merge boolean option is false by default with epc
>  #



  reply	other threads:[~2026-09-23 10:00 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-21 20:57 [PATCH v2 00/10] qapi: convert/split remaining QAPI/QMP intro sections John Snow
2026-09-21 20:57 ` [PATCH v2 02/10] qapi: convert/split intros for block-core.json commands John Snow
2026-09-23  8:50   ` Markus Armbruster
2026-09-25 17:15     ` John Snow
2026-09-26  5:57       ` Markus Armbruster
2026-09-21 20:57 ` [PATCH v2 04/10] qapi: convert/split intros for job.json commands John Snow
2026-09-23  9:20   ` Markus Armbruster
2026-09-23 19:35     ` John Snow
2026-09-21 20:57 ` [PATCH v2 06/10] qapi: convert/split intros for commands John Snow
2026-09-23 11:06   ` Markus Armbruster
2026-09-21 20:57 ` [PATCH v2 09/10] qapi: split intro sections for data structs John Snow
2026-09-23 10:48   ` Markus Armbruster
2026-09-23 21:17     ` John Snow
2026-09-21 20:57 ` [PATCH v2 10/10] qapi: split intro sections for inlinable structs John Snow
2026-09-23  9:59   ` Markus Armbruster [this message]
     [not found] ` <20260921205712.1862167-4-jsnow@redhat.com>
2026-09-23  9:17   ` [PATCH v2 03/10] qapi: convert/split intros for block commands Markus Armbruster
2026-09-28 14:32     ` Eric Blake
2026-09-28 18:00       ` John Snow
     [not found] ` <20260921205712.1862167-6-jsnow@redhat.com>
2026-09-23  9:21   ` [PATCH v2 05/10] qapi: convert/split intros for misc-i386.json commands 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=87se30uw3h.fsf@pond.sub.org \
    --to=armbru@redhat.com \
    --cc=anisinha@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=jsnow@redhat.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.