From: Mark Rustad <[email protected]>

Since the syscall table intentionally uses override initialization,
simply silence those warnings.

CC: Thomas Gleixner <[email protected]>
CC: Ingo Molnar <[email protected]>
CC: "H. Peter Anvin" <[email protected]>
CC: <[email protected]>
CC: Brian Norris <[email protected]>
Signed-off-by: Mark Rustad <[email protected]>
Signed-off-by: Jeff Kirsher <[email protected]>
---
 arch/x86/ia32/syscall_ia32.c | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/arch/x86/ia32/syscall_ia32.c b/arch/x86/ia32/syscall_ia32.c
index 4754ba0..7bc553b 100644
--- a/arch/x86/ia32/syscall_ia32.c
+++ b/arch/x86/ia32/syscall_ia32.c
@@ -15,6 +15,7 @@ typedef void (*sys_call_ptr_t)(void);
 
 extern void compat_ni_syscall(void);
 
+DIAG_PUSH DIAG_CLANG_IGNORE(initializer-overrides)
 const sys_call_ptr_t ia32_sys_call_table[__NR_ia32_syscall_max+1] = {
        /*
         * Smells like a compiler bug -- it doesn't work
@@ -23,3 +24,4 @@ const sys_call_ptr_t 
ia32_sys_call_table[__NR_ia32_syscall_max+1] = {
        [0 ... __NR_ia32_syscall_max] = &compat_ni_syscall,
 #include <asm/syscalls_32.h>
 };
+DIAG_POP
-- 
1.9.3

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Reply via email to