From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Greg Ungerer <gerg@uclinux.org>, Andreas Schwab <schwab@linux-m68k.org>
Cc: linux-m68k@vger.kernel.org, linux-kernel@vger.kernel.org,
Geert Uytterhoeven <geert@linux-m68k.org>
Subject: [PATCH v2 3/4] m68k: Wire up direct ipc calls
Date: Mon, 14 Sep 2015 10:56:45 +0200 [thread overview]
Message-ID: <1442221006-2027-4-git-send-email-geert@linux-m68k.org> (raw)
In-Reply-To: <1442221006-2027-1-git-send-email-geert@linux-m68k.org>
Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
---
v2:
- New.
---
arch/m68k/include/asm/unistd.h | 2 +-
arch/m68k/include/uapi/asm/unistd.h | 11 +++++++++++
arch/m68k/kernel/syscalltable.S | 11 +++++++++++
3 files changed, 23 insertions(+), 1 deletion(-)
diff --git a/arch/m68k/include/asm/unistd.h b/arch/m68k/include/asm/unistd.h
index d25d5a5c83cb6d6b..887667ad6a2f9536 100644
--- a/arch/m68k/include/asm/unistd.h
+++ b/arch/m68k/include/asm/unistd.h
@@ -4,7 +4,7 @@
#include <uapi/asm/unistd.h>
-#define NR_syscalls 374
+#define NR_syscalls 385
#define __ARCH_WANT_OLD_READDIR
#define __ARCH_WANT_OLD_STAT
diff --git a/arch/m68k/include/uapi/asm/unistd.h b/arch/m68k/include/uapi/asm/unistd.h
index 0eebb28488eced36..98298206127d0930 100644
--- a/arch/m68k/include/uapi/asm/unistd.h
+++ b/arch/m68k/include/uapi/asm/unistd.h
@@ -379,5 +379,16 @@
#define __NR_recvmmsg 371
#define __NR_sendmmsg 372
#define __NR_userfaultfd 373
+#define __NR_msgget 374
+#define __NR_msgctl 375
+#define __NR_msgrcv 376
+#define __NR_msgsnd 377
+#define __NR_semget 378
+#define __NR_semctl 379
+#define __NR_semtimedop 380
+#define __NR_shmget 381
+#define __NR_shmctl 382
+#define __NR_shmat 383
+#define __NR_shmdt 384
#endif /* _UAPI_ASM_M68K_UNISTD_H_ */
diff --git a/arch/m68k/kernel/syscalltable.S b/arch/m68k/kernel/syscalltable.S
index 7b5a315f6df2c770..dd6de8bb9b7c7aa4 100644
--- a/arch/m68k/kernel/syscalltable.S
+++ b/arch/m68k/kernel/syscalltable.S
@@ -394,3 +394,14 @@ ENTRY(sys_call_table)
.long sys_recvmmsg
.long sys_sendmmsg
.long sys_userfaultfd
+ .long sys_msgget
+ .long sys_msgctl /* 375 */
+ .long sys_msgrcv
+ .long sys_msgsnd
+ .long sys_semget
+ .long sys_semctl
+ .long sys_semtimedop /* 380 */
+ .long sys_shmget
+ .long sys_shmctl
+ .long sys_shmat
+ .long sys_shmdt
--
1.9.1
next prev parent reply other threads:[~2015-09-14 8:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-14 8:56 [PATCH v2 0/4] m68k: System call updates Geert Uytterhoeven
2015-09-14 8:56 ` [PATCH v2 1/4] m68k: Wire up direct socket calls Geert Uytterhoeven
2015-09-14 8:56 ` [PATCH v2 2/4] m68k: Wire up userfaultfd Geert Uytterhoeven
2015-09-14 8:56 ` Geert Uytterhoeven [this message]
2015-09-14 12:14 ` [PATCH v2 3/4] m68k: Wire up direct ipc calls Greg Ungerer
2015-09-14 8:56 ` [PATCH v2 4/4] m68k: Wire up membarrier Geert Uytterhoeven
[not found] ` <1442221006-2027-4-git-send-email-geert__19660.9066486873$1442221083$gmane$org@linux-m68k.org>
2015-09-17 14:34 ` [PATCH v2 3/4] m68k: Wire up direct ipc calls Andreas Schwab
[not found] ` <CAMuHMdUncyXjxkS99SDTjx0-sU26jtCmFuHeU1=0DoqZL2AWvQ@mail.gmail.com>
[not found] ` <mvmvbb9krpd.fsf@hawking.suse.de>
2015-09-17 15:18 ` Geert Uytterhoeven
2015-09-17 15:39 ` Andreas Schwab
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1442221006-2027-4-git-send-email-geert@linux-m68k.org \
--to=geert@linux-m68k.org \
--cc=gerg@uclinux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=schwab@linux-m68k.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®