From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>
Cc: Linux Kernel Development <linux-kernel@vger.kernel.org>,
Greg Ungerer <gerg@snapgear.com>,
Geert Uytterhoeven <geert@linux-m68k.org>
Subject: [PATCH 1/2] m68k syscall updates
Date: Mon, 9 Oct 2006 22:02:25 +0200 [thread overview]
Message-ID: <200610092002.k99K2P2W031156@anakin.of.borg> (raw)
Add some missing system calls (recent udev needs them)
Signed-Off-By: Kars de Jong <jongk@linux-m68k.org>
Signed-Off-By: Geert Uytterhoeven <geert@linux-m68k.org>
---
arch/m68k/kernel/entry.S | 5 +++++
include/asm-m68k/unistd.h | 7 ++++++-
2 files changed, 11 insertions(+), 1 deletion(-)
--- linux/arch/m68k/kernel/entry.S 2006/01/31 00:57:35 1.26
+++ linux/arch/m68k/kernel/entry.S 2006/02/11 16:28:36 1.27
@@ -707,4 +707,9 @@ sys_call_table:
.long sys_add_key
.long sys_request_key /* 280 */
.long sys_keyctl
+ .long sys_ioprio_set
+ .long sys_ioprio_get
+ .long sys_inotify_init
+ .long sys_inotify_add_watch /* 285 */
+ .long sys_inotify_rm_watch
--- linux/include/asm-m68k/unistd.h 2006/01/14 23:16:33 1.1.1.14
+++ linux/include/asm-m68k/unistd.h 2006/02/11 16:28:36 1.10
@@ -284,10 +284,15 @@
#define __NR_add_key 279
#define __NR_request_key 280
#define __NR_keyctl 281
+#define __NR_ioprio_set 282
+#define __NR_ioprio_get 283
+#define __NR_inotify_init 284
+#define __NR_inotify_add_watch 285
+#define __NR_inotify_rm_watch 286
#ifdef __KERNEL__
-#define NR_syscalls 282
+#define NR_syscalls 287
#include <linux/err.h>
/* user-visible error numbers are in the range -1 - -124: see
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
reply other threads:[~2006-10-09 20:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200610092002.k99K2P2W031156@anakin.of.borg \
--to=geert@linux-m68k.org \
--cc=akpm@osdl.org \
--cc=gerg@snapgear.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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®