From: Riku Voipio <riku.voipio@iki.fi>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-trivial@nongnu.org, Anthony Liguori <aliguori@us.ibm.com>,
Riku Voipio <riku.voipio@iki.fi>,
qemu-devel@nongnu.org, patches@linaro.org
Subject: Re: [Qemu-trivial] [PATCH] linux-user: fix compile error due to stray colon at end of #ifdef line
Date: Mon, 22 Apr 2013 09:38:18 +0300 [thread overview]
Message-ID: <20130422063818.GA13425@afflict.kos.to> (raw)
In-Reply-To: <1366547403-16480-1-git-send-email-peter.maydell@linaro.org>
On Sun, Apr 21, 2013 at 01:30:03PM +0100, Peter Maydell wrote:
> Remove a stray colon from the end of a #ifdef line. Some versions
> of gcc complain about this:
> linux-user/syscall.c: In function ‘do_syscall’:
> linux-user/syscall.c:7606:28: error: extra tokens at end of #ifdef directive [-Werror]
>
> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
Acked-By: Riku Voipio <riku.voipio@linaro.org>
> ---
> Obviously this is 1.5 material; don't care whether it goes through
> linux-user or qemu-trivial or direct commit.
>
> linux-user/syscall.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/linux-user/syscall.c b/linux-user/syscall.c
> index c705960..30e93bc 100644
> --- a/linux-user/syscall.c
> +++ b/linux-user/syscall.c
> @@ -7603,7 +7603,7 @@ abi_long do_syscall(void *cpu_env, int num, abi_long arg1,
> #endif
> #else
> case TARGET_NR_sendfile:
> -#ifdef TARGET_NR_sendfile64:
> +#ifdef TARGET_NR_sendfile64
> case TARGET_NR_sendfile64:
> #endif
> goto unimplemented;
> --
> 1.7.11.4
prev parent reply other threads:[~2013-04-22 6:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1366547403-16480-1-git-send-email-peter.maydell@linaro.org>
2013-04-21 12:46 ` [Qemu-trivial] [Qemu-devel] [PATCH] linux-user: fix compile error due to stray colon at end of #ifdef line Peter Maydell
2013-04-22 6:38 ` Riku Voipio [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=20130422063818.GA13425@afflict.kos.to \
--to=riku.voipio@iki.fi \
--cc=aliguori@us.ibm.com \
--cc=patches@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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).