All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/2] slirp: remove fd_block/fd_nonblock
Date: Wed, 28 Mar 2012 20:47:49 +0200	[thread overview]
Message-ID: <4F735CD5.6080102@siemens.com> (raw)
In-Reply-To: <1332374573-6137-1-git-send-email-pbonzini@redhat.com>

On 2012-03-22 01:02, Paolo Bonzini wrote:
> 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(-)
> 

Thanks, applied to the slirp queue.

Jan

-- 
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux

      parent reply	other threads:[~2012-03-28 18:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-22  0:02 [Qemu-devel] [PATCH 0/2] slirp: remove fd_block/fd_nonblock Paolo Bonzini
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 ` Jan Kiszka [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=4F735CD5.6080102@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=pbonzini@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.