From: Stefan Hajnoczi <stefanha@redhat.com>
To: Liu Ping Fan <pingfank@linux.vnet.ibm.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
qemu-devel@nongnu.org, Anthony Liguori <anthony@codemonkey.ws>,
mdroth <mdroth@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [RFC PATCH v3 0/5] port network layer onto glib
Date: Tue, 9 Apr 2013 17:22:46 +0200 [thread overview]
Message-ID: <20130409152246.GC12456@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <1365399368-26967-1-git-send-email-pingfank@linux.vnet.ibm.com>
On Mon, Apr 08, 2013 at 01:36:03PM +0800, Liu Ping Fan wrote:
> This series focus on network backend (excluding slirp). The related patch
> for core's re-entrant (queue.c net.c) will be sent out separatelly.
Are changes required to tap-win32.c?
Are you working on converting slirp?
Stefan
next prev parent reply other threads:[~2013-04-09 15:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-08 5:36 [Qemu-devel] [RFC PATCH v3 0/5] port network layer onto glib Liu Ping Fan
2013-04-08 5:36 ` [Qemu-devel] [RFC PATCH v3 1/5] net: introduce glib function for network Liu Ping Fan
2013-04-09 14:03 ` Stefan Hajnoczi
2013-04-08 5:36 ` [Qemu-devel] [RFC PATCH v3 2/5] net: port tap onto glib Liu Ping Fan
2013-04-08 5:36 ` [Qemu-devel] [RFC PATCH v3 3/5] net: resolve race of tap backend and its peer Liu Ping Fan
2013-04-08 5:36 ` [Qemu-devel] [RFC PATCH v3 4/5] net: port vde onto glib Liu Ping Fan
2013-04-08 5:36 ` [Qemu-devel] [RFC PATCH v3 5/5] net: port socket to glib Liu Ping Fan
2013-04-09 15:22 ` Stefan Hajnoczi [this message]
2013-04-10 7:47 ` [Qemu-devel] [RFC PATCH v3 0/5] port network layer onto glib liu ping fan
2013-04-10 11:55 ` Stefan Hajnoczi
2013-04-11 9:13 ` liu ping fan
2013-04-11 11:44 ` Stefan Hajnoczi
2013-04-11 12:05 ` liu ping fan
2013-04-12 7:44 ` Stefan Hajnoczi
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=20130409152246.GC12456@stefanha-thinkpad.redhat.com \
--to=stefanha@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=mdroth@linux.vnet.ibm.com \
--cc=pbonzini@redhat.com \
--cc=pingfank@linux.vnet.ibm.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).