From: Stefan Hajnoczi <stefanha@gmail.com>
To: Stefan Weil <weil@mail.berlios.de>
Cc: qemu-trivial@nongnu.org, QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [Qemu-trivial] [PATCH] w32: Remove redundant definitions of PRI*64
Date: Fri, 24 Jun 2011 11:51:03 +0100 [thread overview]
Message-ID: <20110624105103.GA5985@stefanha-thinkpad.localdomain> (raw)
In-Reply-To: <1308910549-4445-1-git-send-email-weil@mail.berlios.de>
On Fri, Jun 24, 2011 at 12:15:49PM +0200, Stefan Weil wrote:
> The PRI*64 macros are defined in MinGW's inttypes.h since 2002,
> so they are not needed in qemu-common.h (which includes inttypes.h).
>
> Signed-off-by: Stefan Weil <weil@mail.berlios.de>
> ---
> qemu-common.h | 5 -----
> 1 files changed, 0 insertions(+), 5 deletions(-)
Thanks, applied to the trivial patches tree:
http://repo.or.cz/w/qemu/stefanha.git/shortlog/refs/heads/trivial-patches
Stefan
prev parent reply other threads:[~2011-06-24 10:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1308896356-17797-1-git-send-email-weil@mail.berlios.de>
2011-06-24 10:15 ` [Qemu-devel] [PATCH] w32: Remove redundant definitions of PRI*64 Stefan Weil
2011-06-24 10:51 ` Stefan Hajnoczi [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=20110624105103.GA5985@stefanha-thinkpad.localdomain \
--to=stefanha@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=weil@mail.berlios.de \
/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).