From: TeLeMan <geleman@gmail.com>
To: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] [PATCH] fix chardev_init for win32
Date: Tue, 5 Jan 2010 09:45:34 +0800 [thread overview]
Message-ID: <a38b25541001041745hf825a20j3697f46d4bc5f184@mail.gmail.com> (raw)
Before calling chardev_init_func(), socket_init() should be called on win32.
---
vl.c | 8 ++++----
1 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/vl.c b/vl.c
index 0f59142..3b39cad 100644
--- a/vl.c
+++ b/vl.c
@@ -5768,6 +5768,10 @@ int main(int argc, char **argv, char **envp)
if (default_vga)
vga_interface_type = VGA_CIRRUS;
+#ifdef _WIN32
+ socket_init();
+#endif
+
if (qemu_opts_foreach(&qemu_chardev_opts, chardev_init_func, NULL, 1) != 0)
exit(1);
@@ -5873,10 +5877,6 @@ int main(int argc, char **argv, char **envp)
init_icount_adjust();
}
-#ifdef _WIN32
- socket_init();
-#endif
-
if (net_init_clients() < 0) {
exit(1);
}
--
1.6.5.1.1367.gcd48
next reply other threads:[~2010-01-05 19:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-05 1:45 TeLeMan [this message]
2010-01-08 16:50 ` [Qemu-devel] [PATCH] fix chardev_init for win32 Anthony Liguori
-- strict thread matches above, loose matches on Subject: below --
2010-04-15 4:37 TeLeMan
2010-05-18 17:57 ` Aurelien Jarno
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=a38b25541001041745hf825a20j3697f46d4bc5f184@mail.gmail.com \
--to=geleman@gmail.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).