qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org
Subject: [PULL 00/10] QAPI patches patches for 2022-04-05
Date: Tue,  5 Apr 2022 12:34:45 +0200	[thread overview]
Message-ID: <20220405103455.4145273-1-armbru@redhat.com> (raw)

I double-checked these patches affect *only* generated documentation.
Safe enough for 7.0, I think.  But I'm quite content to hold on to
them until after the release, if that's preferred.

The following changes since commit 20661b75ea6093f5e59079d00a778a972d6732c5:

  Merge tag 'pull-ppc-20220404' of https://github.com/legoater/qemu into staging (2022-04-04 15:48:55 +0100)

are available in the Git repository at:

  git://repo.or.cz/qemu/armbru.git tags/pull-qapi-2022-04-05

for you to fetch changes up to 8230f3389c7d7215d0c3946d415f54b3e9c07f73:

  qapi: Fix calc-dirty-rate example (2022-04-05 12:30:45 +0200)

----------------------------------------------------------------
QAPI patches patches for 2022-04-05

----------------------------------------------------------------
Markus Armbruster (1):
      qapi: Fix calc-dirty-rate example

Victor Toso (9):
      qapi: fix example of netdev_add command
      qapi: fix examples: replay-break and replay-seek
      qapi: fix example of query-named-block-nodes command
      qapi: fix example of query-spice command
      qapi: fix example of query-vnc command
      qapi: fix example of query-colo-status command
      qapi: fix example of trace-event-get-state command
      qapi: fix example of query-cpus-fast command
      qapi: fix example of query-memdev command

 qapi/block-core.json | 1 +
 qapi/machine.json    | 4 ++--
 qapi/migration.json  | 4 ++--
 qapi/net.json        | 2 +-
 qapi/replay.json     | 4 ++--
 qapi/trace.json      | 2 +-
 qapi/ui.json         | 3 +++
 7 files changed, 12 insertions(+), 8 deletions(-)

-- 
2.35.1



             reply	other threads:[~2022-04-05 10:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-05 10:34 Markus Armbruster [this message]
2022-04-05 10:34 ` [PULL 01/10] qapi: fix example of netdev_add command Markus Armbruster
2022-04-05 10:34 ` [PULL 02/10] qapi: fix examples: replay-break and replay-seek Markus Armbruster
2022-04-05 10:34 ` [PULL 03/10] qapi: fix example of query-named-block-nodes command Markus Armbruster
2022-04-05 10:34 ` [PULL 04/10] qapi: fix example of query-spice command Markus Armbruster
2022-04-05 10:34 ` [PULL 05/10] qapi: fix example of query-vnc command Markus Armbruster
2022-04-05 10:34 ` [PULL 06/10] qapi: fix example of query-colo-status command Markus Armbruster
2022-04-05 10:34 ` [PULL 07/10] qapi: fix example of trace-event-get-state command Markus Armbruster
2022-04-05 10:34 ` [PULL 08/10] qapi: fix example of query-cpus-fast command Markus Armbruster
2022-04-05 10:34 ` [PULL 09/10] qapi: fix example of query-memdev command Markus Armbruster
2022-04-05 10:34 ` [PULL 10/10] qapi: Fix calc-dirty-rate example Markus Armbruster
2022-04-05 15:14 ` [PULL 00/10] QAPI patches patches for 2022-04-05 Peter Maydell

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=20220405103455.4145273-1-armbru@redhat.com \
    --to=armbru@redhat.com \
    --cc=peter.maydell@linaro.org \
    --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).