qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin <mlspirat42@gmail.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: andreas.faerber@web.de, jan.kiszka@web.de, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v3] Support for UDP unicast network backend
Date: Wed, 11 Jan 2012 01:21:20 +0900	[thread overview]
Message-ID: <4F0C6580.3000908@gmail.com> (raw)
In-Reply-To: <CAJSP0QWbcwUFv-0yMx7hvJcsi+X3+VeLvpJA73OEK1taKXbtvw@mail.gmail.com>

On 11/29/11 20:52, Stefan Hajnoczi wrote:
> On Tue, Nov 29, 2011 at 7:55 PM, Benjamin<mlspirat42@gmail.com>  wrote:
>>
>> Signed-off-by: Benjamin<mlspirat42@gmail.com>
>> ---
>>   net.c           |    6 ++++-
>>   net/socket.c    |   73 +++++++++++++++++++++++++++++++++++++++++++++++++++++-
>>   qemu-options.hx |    2 +
>>   3 files changed, 78 insertions(+), 3 deletions(-)
>
> Reviewed-by: Stefan Hajnoczi<stefanha@linux.vnet.ibm.com>
>
>> +    s = net_socket_fd_init(vlan, model, name, fd, 0);
>> +    if (!s) {
>> +        return -1;
>> +    }
>
> I'll add a TODO to my list about net_socket_fd_init().  It does not
> consistently take ownership of fd.  It may return NULL without closing
> it, but then again it might close it on error in another code path :(.
>   Don't worry about this for now.
>
> Stefan

Me again, is it supposed to take that long before the patch is
accepted? Did I forget something?

Regards,

Benjamin

  reply	other threads:[~2012-01-10  7:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-29 19:55 [Qemu-devel] [PATCH v3] Support for UDP unicast network backend Benjamin
2011-11-29 11:52 ` Stefan Hajnoczi
2012-01-10 16:21   ` Benjamin [this message]
2012-01-10 10:59     ` Andreas Färber
2012-01-10 11:11       ` Stefan Hajnoczi
2012-01-06 19:16 ` Kamil Rytarowski
2012-01-06 19:46   ` 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=4F0C6580.3000908@gmail.com \
    --to=mlspirat42@gmail.com \
    --cc=andreas.faerber@web.de \
    --cc=jan.kiszka@web.de \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.com \
    /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).