sh: Avoid exporting unimplemented syscalls.
authorPaul Mundt <lethal@linux-sh.org>
Wed, 28 Mar 2012 07:20:20 +0000 (16:20 +0900)
committerPaul Mundt <lethal@linux-sh.org>
Wed, 28 Mar 2012 07:20:20 +0000 (16:20 +0900)
commit9b2ffa8d048656baf7f5e764d2586ba59927a25b
tree1102eb8f5d5da88bb0747a5adb156f0f68953e0e
parent10a068f27ac2200c83f6d13f5e03f6e48cf06d10
sh: Avoid exporting unimplemented syscalls.

Now that userspace is making use of kernel-provided sanitized headers for
working out supported interfaces, we need to be a bit more diligent with
matching the syscall definitions with their actual wiring/support state.

In theory it shouldn't hurt anything since sys_ni_syscall will ultimately
do the right thing, but there's also not much need to lie about legacy
x86 syscalls that we've never supported.

This tightens things up a bit for uClibc at least.

Suggested-by: Carmelo Amoroso <carmelo.amoroso@st.com>
Acked-by: Mike Frysinger <vapier@gentoo.org>
Signed-off-by: Paul Mundt <lethal@linux-sh.org>
arch/sh/include/asm/unistd_32.h
arch/sh/include/asm/unistd_64.h
arch/sh/kernel/syscalls_32.S
arch/sh/kernel/syscalls_64.S