From: Markus Armbruster <armbru@redhat.com>
To: qemu-devel@nongnu.org
Cc: eblake@redhat.com
Subject: [PATCH 0/6] qapi: Tidy up doc comments
Date: Thu, 20 Jul 2023 09:16:03 +0200 [thread overview]
Message-ID: <20230720071610.1096458-1-armbru@redhat.com> (raw)
This series only affects generated documentation. Generated code does
not change. Would be nice to get it into the release.
Markus Armbruster (6):
qapi/block-core: Tidy up BlockLatencyHistogramInfo documentation
qapi/block: Tidy up block-latency-histogram-set documentation
qapi/qdev: Tidy up device_add documentation
qapi/trace: Tidy up trace-event-get-state, -set-state documentation
qapi: Correct "eg." to "e.g." in documentation
qapi: Reformat recent doc comments to conform to current conventions
qapi/block-core.json | 85 +++++++++++++++++++---------------------
qapi/block.json | 12 +++---
qapi/char.json | 2 +-
qapi/cxl.json | 4 +-
qapi/machine-target.json | 2 +-
qapi/migration.json | 10 ++---
qapi/misc.json | 2 +-
qapi/net.json | 1 -
qapi/qdev.json | 6 +--
qapi/qom.json | 9 +++--
qapi/trace.json | 9 ++---
qapi/ui.json | 2 +-
12 files changed, 68 insertions(+), 76 deletions(-)
--
2.41.0
next reply other threads:[~2023-07-20 7:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-20 7:16 Markus Armbruster [this message]
2023-07-20 7:16 ` [PATCH 1/6] qapi/block-core: Tidy up BlockLatencyHistogramInfo documentation Markus Armbruster
2023-07-20 7:16 ` [PATCH 2/6] qapi/block: Tidy up block-latency-histogram-set documentation Markus Armbruster
2023-07-20 13:39 ` Philippe Mathieu-Daudé
2023-07-20 7:16 ` [PATCH 3/6] qapi/qdev: Tidy up device_add documentation Markus Armbruster
2023-07-20 13:42 ` Philippe Mathieu-Daudé
2023-07-20 7:16 ` [PATCH 4/6] qapi/trace: Tidy up trace-event-get-state, -set-state documentation Markus Armbruster
2023-07-20 7:16 ` [PATCH 5/6] qapi: Correct "eg." to "e.g." in documentation Markus Armbruster
2023-07-20 13:41 ` Philippe Mathieu-Daudé
2023-07-20 15:13 ` Markus Armbruster
2023-07-20 7:16 ` [PATCH 6/6] qapi: Reformat recent doc comments to conform to current conventions 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=20230720071610.1096458-1-armbru@redhat.com \
--to=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).