[PATCH 00/10] qapi: convert simple enum intro sections

John Snow posted 10 patches 2 weeks, 3 days ago
Patches applied successfully (tree, apply log)
git fetch https://github.com/patchew-project/qemu tags/patchew/20260909041640.69080-1-jsnow@redhat.com
Maintainers: Eric Blake <eblake@redhat.com>, Markus Armbruster <armbru@redhat.com>, Kevin Wolf <kwolf@redhat.com>, Hanna Reitz <hreitz@redhat.com>, "Daniel P. Berrangé" <berrange@redhat.com>, Jonathan Cameron <jic23@kernel.org>, "Philippe Mathieu-Daudé" <philmd@oss.qualcomm.com>, Zhao Liu <zhao1.liu@intel.com>, Peter Xu <peterx@redhat.com>, Fabiano Rosas <farosas@suse.de>, Alex Williamson <alex@shazbot.org>, "Cédric Le Goater" <clg@redhat.com>, Lukas Straub <lukasstraub2@web.de>
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(-)
[PATCH 00/10] qapi: convert simple enum intro sections
Posted by John Snow 2 weeks, 3 days ago
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

Re: [PATCH 00/10] qapi: convert simple enum intro sections
Posted by Markus Armbruster 2 weeks, 3 days ago
Series
Reviewed-by: Markus Armbruster <armbru@redhat.com>