qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Luiz Capitulino <lcapitulino@redhat.com>
To: peter.maydell@linaro.org
Cc: qemu-devel@nongnu.org, anthony@codemonkey.ws
Subject: [Qemu-devel] [PULL for-2.1 0/8] QMP queue
Date: Fri, 27 Jun 2014 15:41:55 -0400	[thread overview]
Message-ID: <1403898123-22963-1-git-send-email-lcapitulino@redhat.com> (raw)

The following changes since commit d4cba13bdf251baeedb36b87c1e9f6766773e380:

  tcg/ppc: Fix failure in tcg_out_mem_long (2014-06-27 13:23:41 +0100)

are available in the git repository at:

  git://repo.or.cz/qemu/qmp-unstable.git queue/qmp

for you to fetch changes up to a22d8e47f7efb15a96162b92b50f8fb108b1c5d9:

  docs/qmp: Fix documentation of BLOCK_JOB_READY to match code (2014-06-27 13:40:41 -0400)

----------------------------------------------------------------
Laszlo Ersek (2):
      virtio-serial: report frontend connection state via monitor
      char: report frontend open/closed state in 'query-chardev'

Luiz Capitulino (1):
      qmp: add qmp-events.txt back

Markus Armbruster (1):
      docs/qmp: Fix documentation of BLOCK_JOB_READY to match code

Wenchao Xia (4):
      qapi: move event defines
      qapi: ignore generated event files
      qapi script: clean up in scripts
      qapi event: clean up in callers

 .gitignore                              |   1 +
 Makefile                                |   2 +-
 docs/qapi-code-gen.txt                  |   8 +-
 docs/qmp/qmp-events.txt                 | 559 ++++++++++++++++++++++++++++++++
 hw/char/virtio-console.c                |  12 +-
 hw/watchdog/watchdog.c                  |   2 +-
 include/block/blockjob.h                |   2 +-
 monitor.c                               |   3 +-
 qapi-schema.json                        |  20 +-
 qapi/block-core.json                    |   3 +-
 qapi-event.json => qapi/event.json      |  18 +-
 qemu-char.c                             |   1 +
 qmp-commands.hx                         |  19 +-
 scripts/qapi-event.py                   |   5 +-
 scripts/qapi.py                         |   2 +-
 tests/qapi-schema/event-nest-struct.err |   2 +-
 16 files changed, 629 insertions(+), 30 deletions(-)
 create mode 100644 docs/qmp/qmp-events.txt
 rename qapi-event.json => qapi/event.json (94%)

             reply	other threads:[~2014-06-27 19:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-27 19:41 Luiz Capitulino [this message]
2014-06-27 19:41 ` [Qemu-devel] [PULL 1/8] qapi: move event defines Luiz Capitulino
2014-06-27 19:41 ` [Qemu-devel] [PULL 2/8] qapi: ignore generated event files Luiz Capitulino
2014-06-27 19:41 ` [Qemu-devel] [PULL 3/8] qapi script: clean up in scripts Luiz Capitulino
2014-06-27 19:41 ` [Qemu-devel] [PULL 4/8] qapi event: clean up in callers Luiz Capitulino
2014-06-27 19:42 ` [Qemu-devel] [PULL 5/8] qmp: add qmp-events.txt back Luiz Capitulino
2014-06-27 19:42 ` [Qemu-devel] [PULL 6/8] virtio-serial: report frontend connection state via monitor Luiz Capitulino
2014-06-27 19:42 ` [Qemu-devel] [PULL 7/8] char: report frontend open/closed state in 'query-chardev' Luiz Capitulino
2014-06-27 19:42 ` [Qemu-devel] [PULL 8/8] docs/qmp: Fix documentation of BLOCK_JOB_READY to match code Luiz Capitulino
2014-06-29 14:24 ` [Qemu-devel] [PULL for-2.1 0/8] QMP queue 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=1403898123-22963-1-git-send-email-lcapitulino@redhat.com \
    --to=lcapitulino@redhat.com \
    --cc=anthony@codemonkey.ws \
    --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).