From: Yann Quelen <yann.fc.quelen@gmail.com>
To: lode leroy <lode_leroy@hotmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] TAP32 networking on windows
Date: Thu, 19 May 2011 14:45:14 +0200 [thread overview]
Message-ID: <BANLkTikB1Yw_8CgenOUm6ZyuUcwoFZSzBg@mail.gmail.com> (raw)
In-Reply-To: <DUB105-w28752C2C4E3F7B7839BAE5FF8E0@phx.gbl>
Hello,
This patch is already present in the master branch (commit c3febae6).
I confirm it solves the problem for me when applied on version 0.14.0
2011/5/19 lode leroy <lode_leroy@hotmail.com>:
>
> Please consider the patch I submitted on 2010-07-05
> I tried it in qemu-0.14.1 and this makes it work.
>
> https://bugs.launchpad.net/qemu/+bug/589564
>
>
> --- net/tap-win32.c 2010-07-05 11:14:51 +0200
>
> +++ net/tap-win32.c-orig 2010-07-05 11:33:11 +0200
>
> @@ -479,7 +479,7 @@ static int tap_win32_write(tap_win32_ove
>
> }
>
> }
> - return 0;
>
> + return write_size;
>
> }
> static DWORD WINAPI tap_win32_thread_entry(LPVOID param)
>
>
prev parent reply other threads:[~2011-05-19 12:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-19 12:22 [Qemu-devel] TAP32 networking on windows lode leroy
2011-05-19 12:45 ` Yann Quelen [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=BANLkTikB1Yw_8CgenOUm6ZyuUcwoFZSzBg@mail.gmail.com \
--to=yann.fc.quelen@gmail.com \
--cc=lode_leroy@hotmail.com \
--cc=qemu-devel@nongnu.org \
/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).