Commit 79f211b8 authored by Paul Mundt's avatar Paul Mundt

sh64: wire up sys_accept4.

sh64 on the other hand provides both direct broken out syscalls as well
as socketcall access. As there are binaries that use both socketcall has
to stay around. The current ABI prefers direct syscalls.

It was pointed out that when sys_recvmmsg was added in, sys_accept4 was
overlooked. This takes care of wiring it up.
Signed-off-by: default avatarPaul Mundt <lethal@linux-sh.org>
parent 6eacb2c4
...@@ -386,10 +386,11 @@ ...@@ -386,10 +386,11 @@
#define __NR_rt_tgsigqueueinfo 363 #define __NR_rt_tgsigqueueinfo 363
#define __NR_perf_event_open 364 #define __NR_perf_event_open 364
#define __NR_recvmmsg 365 #define __NR_recvmmsg 365
#define __NR_accept4 366
#ifdef __KERNEL__ #ifdef __KERNEL__
#define NR_syscalls 366 #define NR_syscalls 367
#define __ARCH_WANT_IPC_PARSE_VERSION #define __ARCH_WANT_IPC_PARSE_VERSION
#define __ARCH_WANT_OLD_READDIR #define __ARCH_WANT_OLD_READDIR
......
...@@ -392,3 +392,4 @@ sys_call_table: ...@@ -392,3 +392,4 @@ sys_call_table:
.long sys_rt_tgsigqueueinfo .long sys_rt_tgsigqueueinfo
.long sys_perf_event_open .long sys_perf_event_open
.long sys_recvmmsg /* 365 */ .long sys_recvmmsg /* 365 */
.long sys_accept4
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment