[<prev] [next>] [day] [month] [year] [list]
Message-ID: <tip-9271b0b4b2044c6db06051fe60bc58cdd4f17c7c@git.kernel.org>
Date: Sun, 10 Jun 2012 10:43:38 -0700
From: tip-bot for Martin Pelikan <pelikan@...rkhole.cz>
To: linux-tip-commits@...r.kernel.org
Cc: linux-kernel@...r.kernel.org, hpa@...or.com, mingo@...nel.org,
pelikan@...rkhole.cz, richard@....at, tglx@...utronix.de
Subject: [tip:x86/urgent] x86, um:
Correct syscall table type attributes breaking gcc 4.8
Commit-ID: 9271b0b4b2044c6db06051fe60bc58cdd4f17c7c
Gitweb: http://git.kernel.org/tip/9271b0b4b2044c6db06051fe60bc58cdd4f17c7c
Author: Martin Pelikan <pelikan@...rkhole.cz>
AuthorDate: Sat, 9 Jun 2012 21:22:11 +0200
Committer: H. Peter Anvin <hpa@...or.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@...rkhole.cz>
Link: http://lkml.kernel.org/r/1339269731-10772-1-git-send-email-pelikan@storkhole.cz
Acked-by: Richard Weinberger <richard@....at>
Signed-off-by: H. Peter Anvin <hpa@...or.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 = {
/*
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists