From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org
Cc: jan.kiszka@web.de
Subject: [Qemu-devel] [PATCH 0/2] slirp: remove fd_block/fd_nonblock
Date: Thu, 22 Mar 2012 01:02:50 +0100 [thread overview]
Message-ID: <1332374573-6137-1-git-send-email-pbonzini@redhat.com> (raw)
Of these two functions, one is unused and the other is a dup of
socket_set_nonblock. Unfortunately, there are some conflicts
with system headers that need to be sorted out first.
Paolo Bonzini (2):
slirp: clean up conflicts with system headers
slirp: use socket_set_nonblock
slirp/misc.c | 46 +---------------------------------------------
slirp/slirp.h | 8 +-------
slirp/tcp.h | 21 +++++++++++++++------
slirp/tcp_subr.c | 4 ++--
4 files changed, 19 insertions(+), 60 deletions(-)
--
1.7.9.1
next reply other threads:[~2012-03-22 0:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-22 0:02 Paolo Bonzini [this message]
2012-03-22 0:02 ` [Qemu-devel] [PATCH 1/2] slirp: clean up conflicts with system headers Paolo Bonzini
2012-03-22 14:35 ` Jan Kiszka
2012-03-22 19:24 ` Paolo Bonzini
2012-03-23 9:00 ` Jan Kiszka
2012-03-22 0:02 ` [Qemu-devel] [PATCH 2/2] slirp: use socket_set_nonblock Paolo Bonzini
2012-03-28 18:47 ` [Qemu-devel] [PATCH 0/2] slirp: remove fd_block/fd_nonblock Jan Kiszka
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=1332374573-6137-1-git-send-email-pbonzini@redhat.com \
--to=pbonzini@redhat.com \
--cc=jan.kiszka@web.de \
--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).