From: tip-bot for Martin Pelikan <pelikan@storkhole.cz>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com, mingo@kernel.org,
pelikan@storkhole.cz, richard@nod.at, tglx@linutronix.de
Subject: [tip:x86/urgent] x86, um: Correct syscall table type attributes breaking gcc 4.8
Date: Sun, 10 Jun 2012 10:43:38 -0700 [thread overview]
Message-ID: <tip-9271b0b4b2044c6db06051fe60bc58cdd4f17c7c@git.kernel.org> (raw)
In-Reply-To: <1339269731-10772-1-git-send-email-pelikan@storkhole.cz>
Commit-ID: 9271b0b4b2044c6db06051fe60bc58cdd4f17c7c
Gitweb: http://git.kernel.org/tip/9271b0b4b2044c6db06051fe60bc58cdd4f17c7c
Author: Martin Pelikan <pelikan@storkhole.cz>
AuthorDate: Sat, 9 Jun 2012 21:22:11 +0200
Committer: H. Peter Anvin <hpa@zytor.com>
CommitDate: Sat, 9 Jun 2012 12:51:09 -0700
x86, um: Correct syscall table type attributes breaking gcc 4.8
The latest GCC 4.8 does some more checking on type attributes that
break the build for ARCH=um -> fill them in. Specifically, the
"asmlinkage" attributes is now tested for consistency.
Signed-off-by: Martin Pelikan <pelikan@storkhole.cz>
Link: http://lkml.kernel.org/r/1339269731-10772-1-git-send-email-pelikan@storkhole.cz
Acked-by: Richard Weinberger <richard@nod.at>
Signed-off-by: H. Peter Anvin <hpa@zytor.com>
---
arch/x86/um/sys_call_table_32.c | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/x86/um/sys_call_table_32.c b/arch/x86/um/sys_call_table_32.c
index 416bd40..68d1dc9 100644
--- a/arch/x86/um/sys_call_table_32.c
+++ b/arch/x86/um/sys_call_table_32.c
@@ -39,9 +39,9 @@
#undef __SYSCALL_I386
#define __SYSCALL_I386(nr, sym, compat) [ nr ] = sym,
-typedef void (*sys_call_ptr_t)(void);
+typedef asmlinkage void (*sys_call_ptr_t)(void);
-extern void sys_ni_syscall(void);
+extern asmlinkage void sys_ni_syscall(void);
const sys_call_ptr_t sys_call_table[] __cacheline_aligned = {
/*
parent reply other threads:[~2012-06-10 17:44 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1339269731-10772-1-git-send-email-pelikan@storkhole.cz>]
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=tip-9271b0b4b2044c6db06051fe60bc58cdd4f17c7c@git.kernel.org \
--to=pelikan@storkhole.cz \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=richard@nod.at \
--cc=tglx@linutronix.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