From: "Kazu" <kazoo@r3.dion.ne.jp>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Compile fix for win32
Date: Wed, 8 Feb 2006 12:57:21 +0900 [thread overview]
Message-ID: <001701c62c63$c36fb420$0464a8c0@athlon> (raw)
Hi,
It is compile fix for win32.
Regards,
Kazu
Index: tap-win32.c
===================================================================
RCS file: /sources/qemu/qemu/tap-win32.c,v
retrieving revision 1.1
diff -u -r1.1 tap-win32.c
--- tap-win32.c 1 Feb 2006 23:06:55 -0000 1.1
+++ tap-win32.c 7 Feb 2006 07:25:02 -0000
@@ -671,7 +671,7 @@
return -1;
}
- s->vc = qemu_new_vlan_client(vlan, tap_receive, s);
+ s->vc = qemu_new_vlan_client(vlan, tap_receive, NULL, s);
snprintf(s->vc->info_str, sizeof(s->vc->info_str),
"tap: ifname=%s", ifname);
next reply other threads:[~2006-02-08 3:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-08 3:57 Kazu [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-09-05 5:25 [Qemu-devel] Compile fix for win32 Kazu
2006-08-07 5:05 Kazu
2005-12-19 6:40 Kazu
2005-12-19 18:50 ` Johannes Schindelin
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='001701c62c63$c36fb420$0464a8c0@athlon' \
--to=kazoo@r3.dion.ne.jp \
--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).