sh: Provide a non-multiplexed sys_recvmmsg path.
Now that the rest of the socket calls are provided through their own paths, do the same for sys_recvmmsg. It's unlikely we'll ever be able to kill off the socketcall path, but this at least permits userspace to gradually begin migrating. Signed-off-by: Paul Mundt <lethal@linux-sh.org>
This commit is contained in:
parent
459ebb34bd
commit
51d149be0a
2 changed files with 20 additions and 20 deletions
|
@ -367,13 +367,12 @@
|
|||
#define __NR_getsockopt 354
|
||||
#define __NR_sendmsg 355
|
||||
#define __NR_recvmsg 356
|
||||
#define __NR_recvmmsg 357
|
||||
|
||||
#define NR_syscalls 357
|
||||
#define NR_syscalls 358
|
||||
|
||||
#ifdef __KERNEL__
|
||||
|
||||
#define __IGNORE_recvmmsg
|
||||
|
||||
#define __ARCH_WANT_IPC_PARSE_VERSION
|
||||
#define __ARCH_WANT_OLD_READDIR
|
||||
#define __ARCH_WANT_OLD_STAT
|
||||
|
|
|
@ -374,3 +374,4 @@ ENTRY(sys_call_table)
|
|||
.long sys_getsockopt
|
||||
.long sys_sendmsg /* 355 */
|
||||
.long sys_recvmsg
|
||||
.long sys_recvmmsg
|
||||
|
|
Loading…
Reference in a new issue