All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Andreas Färber" <andreas.faerber@web.de>
To: Benjamin <mlspirat42@gmail.com>, Stefan Hajnoczi <stefanha@gmail.com>
Cc: jan.kiszka@web.de, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v3] Support for UDP unicast network backend
Date: Tue, 10 Jan 2012 11:59:00 +0100	[thread overview]
Message-ID: <4F0C19F4.9040701@web.de> (raw)
In-Reply-To: <4F0C6580.3000908@gmail.com>

Am 10.01.2012 17:21, schrieb Benjamin:
> 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>

A minor nit: the SoB is a legal assertion that you not stole, etc. the
code, and as such it should include first and last name.

>>> ---
>>>   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 :(.

Hasn't this been taken care of in the meantime? Any changes needed for
that, Stefan?

> Me again, is it supposed to take that long before the patch is
> accepted?

Not supposed to, but sometimes it does...

Andreas

  reply	other threads:[~2012-01-10 11:00 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
2012-01-10 10:59     ` Andreas Färber [this message]
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=4F0C19F4.9040701@web.de \
    --to=andreas.faerber@web.de \
    --cc=jan.kiszka@web.de \
    --cc=mlspirat42@gmail.com \
    --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 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.