From: Paolo Bonzini <pbonzini@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v3 0/9] Introduce I/O channels framework
Date: Fri, 11 Dec 2015 12:20:16 +0100 [thread overview]
Message-ID: <566AB170.8040609@redhat.com> (raw)
In-Reply-To: <20151211105321.GA19917@redhat.com>
On 11/12/2015 11:53, Daniel P. Berrange wrote:
> Ping, unless anyone wants to review this further I'll send a pull
> request for it once 2.6 opens up, so I can focus on getting the
> other dependant patch series reviewed & merged in 2.6 too.
Yes, please do.
Paolo
prev parent reply other threads:[~2015-12-11 11:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-18 18:42 [Qemu-devel] [PATCH v3 0/9] Introduce I/O channels framework Daniel P. Berrange
2015-11-18 18:42 ` [Qemu-devel] [PATCH v3 1/9] io: add abstract QIOChannel classes Daniel P. Berrange
2015-11-18 18:42 ` [Qemu-devel] [PATCH v3 2/9] io: add helper module for creating watches on FDs Daniel P. Berrange
2015-11-18 18:42 ` [Qemu-devel] [PATCH v3 3/9] io: add QIOTask class for async operations Daniel P. Berrange
2015-11-18 18:42 ` [Qemu-devel] [PATCH v3 4/9] io: add QIOChannelSocket class Daniel P. Berrange
2015-11-18 18:42 ` [Qemu-devel] [PATCH v3 5/9] io: add QIOChannelFile class Daniel P. Berrange
2015-11-18 18:42 ` [Qemu-devel] [PATCH v3 6/9] io: add QIOChannelTLS class Daniel P. Berrange
2015-11-18 18:42 ` [Qemu-devel] [PATCH v3 7/9] io: add QIOChannelWebsock class Daniel P. Berrange
2015-11-18 18:42 ` [Qemu-devel] [PATCH v3 8/9] io: add QIOChannelCommand class Daniel P. Berrange
2015-11-18 18:42 ` [Qemu-devel] [PATCH v3 9/9] io: add QIOChannelBuffer class Daniel P. Berrange
2015-12-11 10:53 ` [Qemu-devel] [PATCH v3 0/9] Introduce I/O channels framework Daniel P. Berrange
2015-12-11 11:20 ` Paolo Bonzini [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=566AB170.8040609@redhat.com \
--to=pbonzini@redhat.com \
--cc=berrange@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).