From: Stefan Weil <weil@mail.berlios.de>
To: Blue Swirl <blauwirbel@gmail.com>, Anthony Liguori <aliguori@us.ibm.com>
Cc: Tristan Gingold <gingold@adacore.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] qemu-timer.c: fix build on windows.
Date: Mon, 07 Feb 2011 18:26:20 +0100 [thread overview]
Message-ID: <4D502B3C.1030406@mail.berlios.de> (raw)
In-Reply-To: <1297085731-1489-1-git-send-email-gingold@adacore.com>
Am 07.02.2011 14:35, schrieb Tristan Gingold:
> The function qemu_next_alarm_deadline is needed by windows.
>
> Signed-off-by: Tristan Gingold <gingold@adacore.com>
> ---
> qemu-timer.c | 3 +--
> 1 files changed, 1 insertions(+), 2 deletions(-)
[snip]
Maybe one of the maintainers can apply your patch or this
one (which already has Paolo's acknowledge):
http://patchwork.ozlabs.org/patch/81952/
Thanks,
Stefan Weil
prev parent reply other threads:[~2011-02-07 21:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-07 13:35 [Qemu-devel] [PATCH] qemu-timer.c: fix build on windows Tristan Gingold
2011-02-07 17:26 ` Stefan Weil [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=4D502B3C.1030406@mail.berlios.de \
--to=weil@mail.berlios.de \
--cc=aliguori@us.ibm.com \
--cc=blauwirbel@gmail.com \
--cc=gingold@adacore.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).