From: Luiz Capitulino <lcapitulino@redhat.com>
To: Laszlo Ersek <lersek@redhat.com>
Cc: amit.shah@redhat.com, mprivozn@redhat.com, qemu-devel@nongnu.org,
kraxel@redhat.com
Subject: Re: [Qemu-devel] [PATCH for-2.1 v3 0/2] help libvirt know what's up with qga
Date: Fri, 27 Jun 2014 09:36:31 -0400 [thread overview]
Message-ID: <20140627093631.48266b0b@redhat.com> (raw)
In-Reply-To: <1403797803-11984-1-git-send-email-lersek@redhat.com>
On Thu, 26 Jun 2014 17:50:01 +0200
Laszlo Ersek <lersek@redhat.com> wrote:
> Changes in v3: patch 1 creates the event with a "bool" field called
> "open" in the data portion, instead of introducing a two-valued enum.
> Patch 2 is left intact. Retested.
Applied to the qmp branch, thanks for the effort for doing it on time!
>
> Laszlo Ersek (2):
> virtio-serial: report frontend connection state via monitor
> char: report frontend open/closed state in 'query-chardev'
>
> qapi-event.json | 14 ++++++++++++++
> qapi-schema.json | 8 +++++++-
> hw/char/virtio-console.c | 12 +++++++++---
> monitor.c | 1 +
> qemu-char.c | 1 +
> qmp-commands.hx | 19 ++++++++++++++-----
> 6 files changed, 46 insertions(+), 9 deletions(-)
>
prev parent reply other threads:[~2014-06-27 13:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-26 15:50 [Qemu-devel] [PATCH for-2.1 v3 0/2] help libvirt know what's up with qga Laszlo Ersek
2014-06-26 15:50 ` [Qemu-devel] [PATCH for-2.1 v3 1/2] virtio-serial: report frontend connection state via monitor Laszlo Ersek
2014-06-27 4:45 ` Amit Shah
2014-06-27 12:32 ` Luiz Capitulino
2014-06-26 15:50 ` [Qemu-devel] [PATCH for-2.1 v3 2/2] char: report frontend open/closed state in 'query-chardev' Laszlo Ersek
2014-06-26 16:37 ` [Qemu-devel] [PATCH for-2.1 v3 0/2] help libvirt know what's up with qga Eric Blake
2014-06-26 20:16 ` Laszlo Ersek
2014-06-26 20:18 ` Laszlo Ersek
2014-06-27 13:36 ` Luiz Capitulino [this message]
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=20140627093631.48266b0b@redhat.com \
--to=lcapitulino@redhat.com \
--cc=amit.shah@redhat.com \
--cc=kraxel@redhat.com \
--cc=lersek@redhat.com \
--cc=mprivozn@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).