From: Jason Wang <jasowang@redhat.com>
To: Stefan Weil <sw@weilnetz.de>,
Andrew Baumann <Andrew.Baumann@microsoft.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v2 0/2] net/tap-win32 bugfixes
Date: Wed, 25 Nov 2015 16:21:20 +0800 [thread overview]
Message-ID: <56556F80.8070408@redhat.com> (raw)
In-Reply-To: <5655518F.20405@weilnetz.de>
On 11/25/2015 02:13 PM, Stefan Weil wrote:
> Am 25.11.2015 um 04:01 schrieb Jason Wang:
>>
>> On 11/25/2015 07:36 AM, Andrew Baumann wrote:
>>> Ping?
>>>
>>> Jason, I know you planned to leave this for a few days... I just wanted to make sure it isn't forgotten :)
>>>
>>> Thanks,
>>> Andrew
>> Thanks for working on this. I would expect Stefan to review v2 (since he
>> reviewed v1).
>>
>> Stefan, could you please review v2?
>
> Hi Jason,
>
> patch 1/2 already contains my Reviewed-by, but I cannot say
> much about patch 2/2, simply because I cannot test it.
>
> As the changes in 2/2 look plausible, I suggest nevertheless
> to apply both patches for QEMU 2.5. What would be the correct
> way to indicate this? Acked-by: Stefan Weil <sw@weilnetz.de>?
> Feel free to add it to patch 2/2 if needed.
>
> Kind regards,
> Stefan
Thanks for the reviewing.
Apply the series for 2.5 in my -net tree.
prev parent reply other threads:[~2015-11-25 8:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-18 19:45 [Qemu-devel] [PATCH v2 0/2] net/tap-win32 bugfixes Andrew Baumann
2015-11-18 19:45 ` [Qemu-devel] [PATCH v2 1/2] tap-win32: skip unexpected nodes during registry enumeration Andrew Baumann
2015-11-18 19:45 ` [Qemu-devel] [PATCH v2 2/2] tap-win32: disable broken async write path Andrew Baumann
2015-11-24 23:36 ` [Qemu-devel] [PATCH v2 0/2] net/tap-win32 bugfixes Andrew Baumann
2015-11-25 3:01 ` Jason Wang
2015-11-25 6:13 ` Stefan Weil
2015-11-25 8:21 ` Jason Wang [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=56556F80.8070408@redhat.com \
--to=jasowang@redhat.com \
--cc=Andrew.Baumann@microsoft.com \
--cc=qemu-devel@nongnu.org \
--cc=sw@weilnetz.de \
/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.