linux-cxl.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Snow <jsnow@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Markus Armbruster" <armbru@redhat.com>,
	"Peter Xu" <peterx@redhat.com>, "Fabiano Rosas" <farosas@suse.de>,
	qemu-block@nongnu.org, "Eric Blake" <eblake@redhat.com>,
	"Cédric Le Goater" <clg@redhat.com>,
	"Alex Williamson" <alex@shazbot.org>,
	"Daniel P. Berrangé" <berrange@redhat.com>,
	"Jonathan Cameron" <jic23@kernel.org>,
	"Lukas Straub" <lukasstraub2@web.de>,
	"Philippe Mathieu-Daudé" <philmd@mailo.com>,
	"Zhao Liu" <zhao1.liu@intel.com>,
	"Hanna Reitz" <hreitz@redhat.com>,
	linux-cxl@vger.kernel.org, "Kevin Wolf" <kwolf@redhat.com>,
	"John Snow" <jsnow@redhat.com>
Subject: [PATCH 00/10] qapi: convert simple enum intro sections
Date: Wed,  9 Sep 2026 00:16:30 -0400	[thread overview]
Message-ID: <20260909041640.69080-1-jsnow@redhat.com> (raw)

Hello, this work converts "simple" intro sections for enum
definitions 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.)

If you are a non-QAPI maintainer who has been CC'd on this series,
there is likely very little for you to look at in this series. What
you need to know is that indented paragraphs become part of a
command's "intro" and will appear "above the fold" - above additional
detail in our generated QMP documentation (i.e. features, arguments,
return value, errors, etc) and anything else will eventually appear
"below the fold" - below the detail table, alongside examples, notes,
and more verbose prose.

As enum definitions cannot be inlined by any other definition, the
documentation text for enums will never be re-written or reproduced in
any other context. As such, the distinction between "intro" and
"details" are less important here, but the distinction does still
determine where auto-generated documentation will be inserted, if any:
features will always be inserted "after the intro". (Note that at
present, features do not have any stub text that is automatically
generated.)

John Snow (10):
  qapi: convert simple enum intros for vfio.json
  qapi: convert simple enum intros for machine-common.json
  qapi: convert simple enum intros for introspect.json
  qapi: convert simple enum intros for block.json
  qapi: convert simple enum intros for cypto.json
  qapi: convert simple enum intros for cxl.json
  qapi: convert simple enum intros for yank.json
  qapi: convert simple enum intros for migration.json
  qapi: convert simple enum intros for machine.json
  qapi: convert simple enum intros for block-core.json

 qapi/block-core.json     |  7 +++----
 qapi/block.json          |  9 ++++-----
 qapi/crypto.json         | 18 +++++++++---------
 qapi/cxl.json            | 27 ++++++++++++---------------
 qapi/introspect.json     |  5 ++---
 qapi/machine-common.json |  5 ++---
 qapi/machine.json        | 21 +++++++++------------
 qapi/migration.json      | 10 ++++------
 qapi/vfio.json           | 15 +++++++--------
 qapi/yank.json           |  5 ++---
 10 files changed, 54 insertions(+), 68 deletions(-)

-- 
2.55.0



             reply	other threads:[~2026-09-09  4:16 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-09  4:16 John Snow [this message]
2026-09-09  4:16 ` [PATCH 01/10] qapi: convert simple enum intros for vfio.json John Snow
2026-09-09  5:45   ` Cédric Le Goater
2026-09-09  4:16 ` [PATCH 02/10] qapi: convert simple enum intros for machine-common.json John Snow
2026-09-09  4:16 ` [PATCH 03/10] qapi: convert simple enum intros for introspect.json John Snow
2026-09-09  4:16 ` [PATCH 04/10] qapi: convert simple enum intros for block.json John Snow
2026-09-09  4:16 ` [PATCH 05/10] qapi: convert simple enum intros for cypto.json John Snow
2026-09-10  4:47   ` Markus Armbruster
2026-09-09  4:16 ` [PATCH 06/10] qapi: convert simple enum intros for cxl.json John Snow
2026-09-09  4:16 ` [PATCH 07/10] qapi: convert simple enum intros for yank.json John Snow
2026-09-09  4:16 ` [PATCH 08/10] qapi: convert simple enum intros for migration.json John Snow
2026-09-09  4:16 ` [PATCH 09/10] qapi: convert simple enum intros for machine.json John Snow
2026-09-09  4:16 ` [PATCH 10/10] qapi: convert simple enum intros for block-core.json John Snow
2026-09-09  6:31 ` [PATCH 00/10] qapi: convert simple enum 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=20260909041640.69080-1-jsnow@redhat.com \
    --to=jsnow@redhat.com \
    --cc=alex@shazbot.org \
    --cc=armbru@redhat.com \
    --cc=berrange@redhat.com \
    --cc=clg@redhat.com \
    --cc=eblake@redhat.com \
    --cc=farosas@suse.de \
    --cc=hreitz@redhat.com \
    --cc=jic23@kernel.org \
    --cc=kwolf@redhat.com \
    --cc=linux-cxl@vger.kernel.org \
    --cc=lukasstraub2@web.de \
    --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;
as well as URLs for NNTP newsgroup(s).