Linux CXL
 help / color / mirror / Atom feed
From: John Snow <jsnow@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
	"Eric Blake" <eblake@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@mailo.com>,
	"Igor Mammedov" <imammedo@redhat.com>,
	linux-cxl@vger.kernel.org, "Zhao Liu" <zhao1.liu@intel.com>,
	"Kevin Wolf" <kwolf@redhat.com>,
	"Hanna Reitz" <hreitz@redhat.com>,
	"Lukas Straub" <lukasstraub2@web.de>,
	"Markus Armbruster" <armbru@redhat.com>,
	"Jonathan Cameron" <jic23@kernel.org>,
	qemu-block@nongnu.org, "Ani Sinha" <anisinha@redhat.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"John Snow" <jsnow@redhat.com>
Subject: [PATCH 00/10] qapi: convert simple data struct/alternate intro sections
Date: Thu, 10 Sep 2026 16:38:46 -0400	[thread overview]
Message-ID: <20260910203856.99003-1-jsnow@redhat.com> (raw)

Hello, this work converts "simple" intro sections for data struct
definitions (and one alternate) in the QAPI schema to use the new
syntax. This is part of our ongoing effort to add the mythical
"inliner" to our generated QMP documentation.

"simple" here is a non-technical distinction that means a single
paragraph of text followed by an existing section boundary that
naturally already delineates what comprises the intro.
(This is about 25% of the remaining conversions.)

"data struct" is another non-technical distinction that means a QAPI
struct that is not used as a branch, argument definition, or the basis
of another struct. In effect, it is only "data" and as a result, is
not *currently* a candidate to be inlined into any other definition.

Documentation that is to be "inlined"-- to be written into another
definition's documentation-- needs to ensure that the documentation
written in the "intro" segment is not crucial to understanding the
behavior of the individual members. The "intro" does not get inlined,
but the rest of the documentation does. These "data structs" as
isolated in this series currently are not eligible to be inlined. As
such, the precise distinction between intro and details for these
definitions is not presently as crucial - however, these structs may
become inlined in the future, so a closer eye is still warranted.

If you are a non-QAPI maintainer who has been CC'd on this series, you
may wish to review what information is being counted as the "intro"
(The indented paragraph) and keep in mind that in the future, this
text may not be visible to the end-user reading our QMP documentation
if this structure is utilized as the 'base' for another struct, used
as the arguments for a command or event, or used as branch of a
union. This series keeps it pretty simple, and every conversion herein
is being codified as "the intro", i.e. "not crucial to understanding
the behavior of the members of this struct".

John Snow (10):
  qapi: convert simple data struct intros for uefi.json
  qapi: convert simple data struct intros for misc-arm.json
  qapi: convert simple data struct intros for acpi.json
  qapi: convert simple data struct intros for run-state.json
  qapi: convert simple data struct intros for yank.json
  qapi: convert simple data struct intros for cxl.json
  qapi: convert simple data struct intros for virtio.json
  qapi: convert simple data struct intros for machine.json
  qapi: convert simple data struct intros for block-core.json
  qapi: convert simple alternate intros for common.json

 qapi/acpi.json       |  7 +++----
 qapi/block-core.json | 37 ++++++++++++++++---------------------
 qapi/common.json     |  7 +++----
 qapi/cxl.json        |  7 +++----
 qapi/machine.json    | 12 +++++-------
 qapi/misc-arm.json   |  9 ++++-----
 qapi/run-state.json  |  7 +++----
 qapi/uefi.json       |  5 ++---
 qapi/virtio.json     | 37 ++++++++++++++++---------------------
 qapi/yank.json       | 10 ++++------
 10 files changed, 59 insertions(+), 79 deletions(-)

-- 
2.55.0



             reply	other threads:[~2026-09-10 20:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-10 20:38 John Snow [this message]
2026-09-10 20:38 ` [PATCH 01/10] qapi: convert simple data struct intros for uefi.json John Snow
2026-09-10 20:38 ` [PATCH 02/10] qapi: convert simple data struct intros for misc-arm.json John Snow
2026-09-10 20:38 ` [PATCH 03/10] qapi: convert simple data struct intros for acpi.json John Snow
2026-09-11  9:01   ` Markus Armbruster
2026-09-10 20:38 ` [PATCH 04/10] qapi: convert simple data struct intros for run-state.json John Snow
2026-09-10 20:38 ` [PATCH 05/10] qapi: convert simple data struct intros for yank.json John Snow
2026-09-10 20:38 ` [PATCH 06/10] qapi: convert simple data struct intros for cxl.json John Snow
2026-09-10 20:38 ` [PATCH 07/10] qapi: convert simple data struct intros for virtio.json John Snow
2026-09-10 20:38 ` [PATCH 08/10] qapi: convert simple data struct intros for machine.json John Snow
2026-09-11  8:59   ` Markus Armbruster
2026-09-10 20:38 ` [PATCH 09/10] qapi: convert simple data struct intros for block-core.json John Snow
2026-09-10 20:38 ` [PATCH 10/10] qapi: convert simple alternate intros for common.json John Snow
2026-09-11  9:02 ` [PATCH 00/10] qapi: convert simple data struct/alternate 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=20260910203856.99003-1-jsnow@redhat.com \
    --to=jsnow@redhat.com \
    --cc=anisinha@redhat.com \
    --cc=armbru@redhat.com \
    --cc=eblake@redhat.com \
    --cc=hreitz@redhat.com \
    --cc=imammedo@redhat.com \
    --cc=jic23@kernel.org \
    --cc=kwolf@redhat.com \
    --cc=linux-cxl@vger.kernel.org \
    --cc=lukasstraub2@web.de \
    --cc=mst@redhat.com \
    --cc=pbonzini@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