From: Amit Shah <amit.shah@redhat.com>
To: "Marc-André Lureau" <marcandre.lureau@gmail.com>
Cc: qemu-devel@nongnu.org, Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 2/2] spice-char: notify the server when chardev is writable
Date: Tue, 28 Oct 2014 20:21:59 +0530 [thread overview]
Message-ID: <20141028145159.GE27014@grmbl.mre> (raw)
In-Reply-To: <CAJ+F1CLTLSurXg9tK+wBT5zmqq23PPQChHuoKUOogdMqYuZYXg@mail.gmail.com>
On (Mon) 27 Oct 2014 [17:32:31], Marc-André Lureau wrote:
> On Mon, Oct 27, 2014 at 1:43 PM, Amit Shah <amit.shah@redhat.com> wrote:
>
> > Great, so there's no other change required to actually use the
> > functionality in my patch? Does my patch fit your need fine, or do
> > you need to tweak the notification somehow?
> >
> >
> It seems to be working nicely.
>
>
> > It would be great to get your reviewed-by to my patch in case
> > everything's fine.
> >
> > Peter has asked me to update the comments on my patch; I'll fix that
> > up right away since this showed up.
> >
>
> Sure, I'll wait for next updated patch then.
Thanks, just sent a v3 out.
Amit
next prev parent reply other threads:[~2014-10-28 14:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-24 9:00 [Qemu-devel] [PATCH 1/2] virtio-console: notify chardev when writable Marc-André Lureau
2014-10-24 9:00 ` [Qemu-devel] [PATCH 2/2] spice-char: notify the server when chardev is writable Marc-André Lureau
2014-10-27 8:08 ` Gerd Hoffmann
2014-10-27 11:45 ` Marc-André Lureau
2014-10-27 11:57 ` Gerd Hoffmann
2015-05-04 9:31 ` Amit Shah
2015-05-05 9:45 ` Gerd Hoffmann
2014-10-27 12:43 ` Amit Shah
2014-10-27 16:32 ` Marc-André Lureau
2014-10-28 14:51 ` Amit Shah [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-05-05 14:58 [Qemu-devel] [PATCH 1/2] virtio-console: notify chardev when writable Marc-André Lureau
2015-05-05 14:58 ` [Qemu-devel] [PATCH 2/2] spice-char: notify the server when chardev is writable Marc-André Lureau
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=20141028145159.GE27014@grmbl.mre \
--to=amit.shah@redhat.com \
--cc=kraxel@redhat.com \
--cc=marcandre.lureau@gmail.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).