qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: qemu-devel@nongnu.org
Cc: stefanha@redhat.com
Subject: [PULL 00/10] QAPI patches patches for 2022-09-07
Date: Wed,  7 Sep 2022 17:03:17 +0200	[thread overview]
Message-ID: <20220907150327.538464-1-armbru@redhat.com> (raw)

The following changes since commit 946e9bccf12f2bcc3ca471b820738fb22d14fc80:

  Merge tag 'samuel-thibault' of https://people.debian.org/~sthibault/qemu into staging (2022-09-06 08:31:24 -0400)

are available in the Git repository at:

  git://repo.or.cz/qemu/armbru.git tags/pull-qapi-2022-09-07

for you to fetch changes up to 6e7a37ffc230d06852f1a8893097331d39df77c9:

  qapi: fix examples of events missing timestamp (2022-09-07 15:10:13 +0200)

----------------------------------------------------------------
QAPI patches patches for 2022-09-07

----------------------------------------------------------------
Victor Toso (10):
      qapi: fix example of query-ballon command
      qapi: fix example of query-vnc command
      qapi: fix example of query-dump-guest-memory-capability command
      qapi: fix example of BLOCK_JOB_READY event
      qapi: fix example of NIC_RX_FILTER_CHANGED event
      qapi: fix example of DEVICE_UNPLUG_GUEST_ERROR event
      qapi: fix example of MEM_UNPLUG_ERROR event
      qapi: fix examples of blockdev-add with qcow2
      qapi: fix example of query-hotpluggable-cpus command
      qapi: fix examples of events missing timestamp

 qapi/block-core.json | 12 ++++++------
 qapi/dump.json       |  2 +-
 qapi/machine.json    |  8 ++++----
 qapi/migration.json  | 27 +++++++++++++++++++++++----
 qapi/net.json        |  1 -
 qapi/qdev.json       |  3 +--
 qapi/ui.json         |  4 ++--
 7 files changed, 37 insertions(+), 20 deletions(-)

-- 
2.37.2



             reply	other threads:[~2022-09-07 15:05 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-07 15:03 Markus Armbruster [this message]
2022-09-07 15:03 ` [PULL 01/10] qapi: fix example of query-ballon command Markus Armbruster
2022-09-07 15:03 ` [PULL 02/10] qapi: fix example of query-vnc command Markus Armbruster
2022-09-07 15:03 ` [PULL 03/10] qapi: fix example of query-dump-guest-memory-capability command Markus Armbruster
2022-09-07 15:03 ` [PULL 04/10] qapi: fix example of BLOCK_JOB_READY event Markus Armbruster
2022-09-07 15:03 ` [PULL 05/10] qapi: fix example of NIC_RX_FILTER_CHANGED event Markus Armbruster
2022-09-07 15:03 ` [PULL 06/10] qapi: fix example of DEVICE_UNPLUG_GUEST_ERROR event Markus Armbruster
2022-09-07 15:03 ` [PULL 07/10] qapi: fix example of MEM_UNPLUG_ERROR event Markus Armbruster
2022-09-07 15:03 ` [PULL 08/10] qapi: fix examples of blockdev-add with qcow2 Markus Armbruster
2022-09-07 15:03 ` [PULL 09/10] qapi: fix example of query-hotpluggable-cpus command Markus Armbruster
2022-09-07 15:03 ` [PULL 10/10] qapi: fix examples of events missing timestamp Markus Armbruster
2022-09-07 18:43 ` [PULL 00/10] QAPI patches patches for 2022-09-07 Stefan Hajnoczi
2022-09-08 10:58 ` Kevin Wolf
2022-09-08 11:33   ` Markus Armbruster
2022-09-08 11:39     ` Markus Armbruster
2022-09-19 11:39       ` Markus Armbruster
2022-09-30 15:29         ` Markus Armbruster
2022-09-30 17:20           ` 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=20220907150327.538464-1-armbru@redhat.com \
    --to=armbru@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.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).