From: Jason Wang <jasowang@redhat.com>
To: Andrew Baumann <Andrew.Baumann@microsoft.com>, qemu-devel@nongnu.org
Cc: Stefan Weil <sw@weilnetz.de>
Subject: Re: [Qemu-devel] [PATCH 0/2] net/tap-win32 bugfixes
Date: Wed, 18 Nov 2015 10:07:12 +0800 [thread overview]
Message-ID: <564BDD50.4060304@redhat.com> (raw)
In-Reply-To: <1447787363-15216-1-git-send-email-Andrew.Baumann@microsoft.com>
On 11/18/2015 03:09 AM, Andrew Baumann wrote:
> Since I just discovered that you're in feature freeze, I wanted to
> submit two smallish bug fixes for the win32 tap device. The changes
> are independent, but without both fixes the tap device is unusable
> (for me, at least!).
>
> Cheers,
> Andrew
>
The patches looks good, but I'm not familiar with Win32 API, so any
"Acked-by" or "Reviewed-by" is more than appreciated.
Will leave them on the list for several days before applying
Thanks.
prev parent reply other threads:[~2015-11-18 2:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-17 19:09 [Qemu-devel] [PATCH 0/2] net/tap-win32 bugfixes Andrew Baumann
2015-11-17 19:09 ` [Qemu-devel] [PATCH 1/2] tap-win32: skip unexpected nodes during registry enumeration Andrew Baumann
2015-11-18 7:25 ` Stefan Weil
2015-11-17 19:09 ` [Qemu-devel] [PATCH 2/2] tap-win32: disable broken async write path Andrew Baumann
2015-11-18 7:39 ` Stefan Weil
2015-11-18 18:33 ` Andrew Baumann
2015-11-18 2:07 ` 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=564BDD50.4060304@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).