From: Kevin Wolf <kwolf@redhat.com>
To: Dong Xu Wang <wdongxu@linux.vnet.ibm.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] rewrite QEMU_BUILD_BUG_ON
Date: Wed, 08 Feb 2012 13:49:36 +0100 [thread overview]
Message-ID: <4F326F60.5010002@redhat.com> (raw)
In-Reply-To: <1324371827-25099-1-git-send-email-wdongxu@linux.vnet.ibm.com>
Am 20.12.2011 10:03, schrieb Dong Xu Wang:
> From: Dong Xu Wang <wdongxu@linux.vnet.ibm.com>
>
> On some platforms, __LINE__ will not expand to real number in QEMU_BUILD_BUG_ON,
> so if using QEMU_BUILD_BUG_ON twice, compiler will report errors. This patch will
> fix it.
>
> BTW, I got error message on RHEL 6.1/gcc 4.4.5.
>
> Signed-off-by: Dong Xu Wang <wdongxu@linux.vnet.ibm.com>
Thanks, applied to the block branch.
Kevin
prev parent reply other threads:[~2012-02-08 13:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-20 9:03 [Qemu-devel] [PATCH] rewrite QEMU_BUILD_BUG_ON Dong Xu Wang
2011-12-20 10:13 ` Stefan Hajnoczi
2011-12-20 10:47 ` Dong Xu Wang
2011-12-20 12:08 ` Stefan Hajnoczi
2011-12-20 13:12 ` Dong Xu Wang
2011-12-20 13:41 ` Stefan Hajnoczi
2012-01-09 5:26 ` Dong Xu Wang
2012-02-08 12:49 ` Kevin Wolf [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=4F326F60.5010002@redhat.com \
--to=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=wdongxu@linux.vnet.ibm.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).