From: Jason Wang <jasowang@redhat.com>
To: Andrew Baumann <Andrew.Baumann@microsoft.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Stefan Weil <sw@weilnetz.de>
Subject: Re: [Qemu-devel] [PATCH v2 0/2] net/tap-win32 bugfixes
Date: Wed, 25 Nov 2015 11:01:39 +0800 [thread overview]
Message-ID: <56552493.7040001@redhat.com> (raw)
In-Reply-To: <BY2PR0301MB20405D3F50A9FCEF72081A029E060@BY2PR0301MB2040.namprd03.prod.outlook.com>
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?
>> -----Original Message-----
>> From: Andrew Baumann
>> Sent: Wednesday, 18 November 2015 11:45
>> To: qemu-devel@nongnu.org
>> Cc: Jason Wang <jasowang@redhat.com>; Stefan Weil <sw@weilnetz.de>;
>> Andrew Baumann <Andrew.Baumann@microsoft.com>
>> Subject: [PATCH v2 0/2] net/tap-win32 bugfixes
>>
>> Minor revisions to the second patch in the series.
>>
>> Cheers,
>> Andrew
>>
>> Andrew Baumann (2):
>> tap-win32: skip unexpected nodes during registry enumeration
>> tap-win32: disable broken async write path
>>
>> net/tap-win32.c | 49 ++++++++++++++++++++++++++++++++++++++-------
>> ----
>> 1 file changed, 38 insertions(+), 11 deletions(-)
>>
>> --
>> 2.5.3
next prev parent reply other threads:[~2015-11-25 3:01 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 [this message]
2015-11-25 6:13 ` Stefan Weil
2015-11-25 8:21 ` Jason Wang
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=56552493.7040001@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 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).