From: Frediano Ziglio <freddy77@gmail.com>
To: stefanha@gmail.com
Cc: qemu-trivial@nongnu.org, qemu-devel@nongnu.org,
Frediano Ziglio <freddy77@gmail.com>
Subject: [Qemu-devel] [PATCH] make qemu_event_handle static
Date: Sat, 31 Mar 2012 19:32:14 +0100 [thread overview]
Message-ID: <1333218734-23920-1-git-send-email-freddy77@gmail.com> (raw)
Signed-off-by: Frediano Ziglio <freddy77@gmail.com>
---
main-loop.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/main-loop.c b/main-loop.c
index db23de0..fc738d1 100644
--- a/main-loop.c
+++ b/main-loop.c
@@ -164,7 +164,7 @@ static int qemu_signal_init(void)
#else /* _WIN32 */
-HANDLE qemu_event_handle = NULL;
+static HANDLE qemu_event_handle = NULL;
static void dummy_event_handler(void *opaque)
{
--
1.7.4.1
next reply other threads:[~2012-03-31 18:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-31 18:32 Frediano Ziglio [this message]
2012-04-02 13:03 ` [Qemu-devel] [PATCH] make qemu_event_handle static Stefan Hajnoczi
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=1333218734-23920-1-git-send-email-freddy77@gmail.com \
--to=freddy77@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=stefanha@gmail.com \
/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).