qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: qemu-devel@nongnu.org
Cc: richard.henderson@linaro.org
Subject: [PULL v2 00/17] QAPI patches patches for 2023-05-09
Date: Wed, 10 May 2023 10:12:21 +0200	[thread overview]
Message-ID: <20230510081224.3588673-1-armbru@redhat.com> (raw)

The following changes since commit 792f77f376adef944f9a03e601f6ad90c2f891b2:

  Merge tag 'pull-loongarch-20230506' of https://gitlab.com/gaosong/qemu into staging (2023-05-06 08:11:52 +0100)

are available in the Git repository at:

  https://repo.or.cz/qemu/armbru.git tags/pull-qapi-2023-05-09-v2

for you to fetch changes up to a937b6aa739f65f2cae2ad9a7eb65a309ad2a359:

  qapi: Reformat doc comments to conform to current conventions (2023-05-10 10:01:01 +0200)

----------------------------------------------------------------
QAPI patches patches for 2023-05-09

----------------------------------------------------------------
Markus Armbruster (17):
      docs/devel/qapi-code-gen: Clean up use of quotes a bit
      docs/devel/qapi-code-gen: Turn FIXME admonitions into comments
      qapi: Fix crash on stray double quote character
      meson: Fix to make QAPI generator output depend on main.py
      Revert "qapi: BlockExportRemoveMode: move comments to TODO"
      sphinx/qapidoc: Do not emit TODO sections into user manuals
      qapi: Tidy up a slightly awkward TODO comment
      qapi/dump: Indent bulleted lists consistently
      tests/qapi-schema/doc-good: Improve a comment
      tests/qapi-schema/doc-good: Improve argument description tests
      qapi: Fix argument description indentation stripping
      qapi: Rewrite parsing of doc comment section symbols and tags
      qapi: Relax doc string @name: description indentation rules
      qapi: Section parameter @indent is no longer used, drop
      docs/devel/qapi-code-gen: Update doc comment conventions
      qga/qapi-schema: Reformat doc comments to conform to current conventions
      qapi: Reformat doc comments to conform to current conventions

 docs/devel/qapi-code-gen.rst          |   74 +-
 docs/sphinx/qapidoc.py                |    3 +
 meson.build                           |    2 +-
 qapi/acpi.json                        |   50 +-
 qapi/audio.json                       |   93 +-
 qapi/authz.json                       |   29 +-
 qapi/block-core.json                  | 2801 +++++++++++++++++----------------
 qapi/block-export.json                |  244 +--
 qapi/block.json                       |  214 +--
 qapi/char.json                        |  134 +-
 qapi/common.json                      |   19 +-
 qapi/compat.json                      |   13 +-
 qapi/control.json                     |   59 +-
 qapi/crypto.json                      |  261 +--
 qapi/cryptodev.json                   |    3 +
 qapi/cxl.json                         |   74 +-
 qapi/dump.json                        |   78 +-
 qapi/error.json                       |    6 +-
 qapi/introspect.json                  |   89 +-
 qapi/job.json                         |  139 +-
 qapi/machine-target.json              |  303 ++--
 qapi/machine.json                     |  389 ++---
 qapi/migration.json                   | 1120 +++++++------
 qapi/misc-target.json                 |   67 +-
 qapi/misc.json                        |  180 +--
 qapi/net.json                         |  260 ++-
 qapi/pci.json                         |   35 +-
 qapi/qapi-schema.json                 |   25 +-
 qapi/qdev.json                        |   63 +-
 qapi/qom.json                         |  404 ++---
 qapi/rdma.json                        |    1 -
 qapi/replay.json                      |   48 +-
 qapi/rocker.json                      |   20 +-
 qapi/run-state.json                   |  227 +--
 qapi/sockets.json                     |   50 +-
 qapi/stats.json                       |   83 +-
 qapi/tpm.json                         |   20 +-
 qapi/trace.json                       |   34 +-
 qapi/transaction.json                 |   87 +-
 qapi/ui.json                          |  435 ++---
 qapi/virtio.json                      |   84 +-
 qapi/yank.json                        |   42 +-
 qga/qapi-schema.json                  |  668 ++++----
 scripts/qapi/parser.py                |  141 +-
 tests/qapi-schema/doc-bad-indent.err  |    2 +-
 tests/qapi-schema/doc-bad-indent.json |    3 +-
 tests/qapi-schema/doc-good.json       |   20 +-
 tests/qapi-schema/doc-good.out        |   19 +-
 48 files changed, 4837 insertions(+), 4378 deletions(-)

-- 
2.39.2



             reply	other threads:[~2023-05-10  8:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-10  8:12 Markus Armbruster [this message]
2023-05-10  8:12 ` [PULL v2 12/17] qapi: Rewrite parsing of doc comment section symbols and tags Markus Armbruster
2023-05-16 12:07   ` Igor Mammedov
2023-05-16 13:59     ` Markus Armbruster
2023-05-10  8:12 ` [PULL v2 13/17] qapi: Relax doc string @name: description indentation rules Markus Armbruster
2023-05-10  8:12 ` [PULL v2 14/17] qapi: Section parameter @indent is no longer used, drop Markus Armbruster
2023-05-10 13:51 ` [PULL v2 00/17] QAPI patches patches for 2023-05-09 Richard Henderson
2023-05-10 14:59 ` Richard Henderson
2023-05-10 15:22   ` Markus Armbruster
2023-05-11 11:11     ` Markus Armbruster
2023-05-11 11:17       ` Richard Henderson

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=20230510081224.3588673-1-armbru@redhat.com \
    --to=armbru@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.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).