public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Love <rlove@rlove.org>
To: Mr Morton <akpm@osdl.org>
Cc: The Cutch <ttb@tentacle.dhs.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [patch] SH64: inotify and ioprio syscalls
Date: Wed, 10 Aug 2005 16:13:17 -0400	[thread overview]
Message-ID: <1123704797.23297.13.camel@betsy> (raw)

Add inotify and ioprio syscall stubs to SH64.

	Robert Love


Signed-off-by: Robert Love <rml@novell.com>

 arch/sh64/kernel/syscalls.S |    5 +++++
 include/asm-sh64/unistd.h   |    7 ++++++-
 2 files changed, 11 insertions(+), 1 deletion(-)

diff -urN linux-2.6.13-rc6-git2/arch/sh64/kernel/syscalls.S linux/arch/sh64/kernel/syscalls.S
--- linux-2.6.13-rc6-git2/arch/sh64/kernel/syscalls.S	2005-06-17 15:48:29.000000000 -0400
+++ linux/arch/sh64/kernel/syscalls.S	2005-08-10 16:12:24.000000000 -0400
@@ -342,4 +342,9 @@
 	.long sys_add_key
 	.long sys_request_key
 	.long sys_keyctl		/* 315 */
+	.long sys_ioprio_set
+	.long sys_ioprio_get
+	.long sys_inotify_init
+	.long sys_inotify_add_watch
+	.long sys_inotify_rm_watch	/* 320 */
 
diff -urN linux-2.6.13-rc6-git2/include/asm-sh64/unistd.h linux/include/asm-sh64/unistd.h
--- linux-2.6.13-rc6-git2/include/asm-sh64/unistd.h	2005-06-17 15:48:29.000000000 -0400
+++ linux/include/asm-sh64/unistd.h	2005-08-10 16:12:10.000000000 -0400
@@ -338,8 +338,13 @@
 #define __NR_add_key		313
 #define __NR_request_key	314
 #define __NR_keyctl		315
+#define __NR_ioprio_set		316
+#define __NR_ioprio_get		317
+#define __NR_inotify_init	318
+#define __NR_inotify_add_watch	319
+#define __NR_inotify_rm_watch	320
 
-#define NR_syscalls 316
+#define NR_syscalls 321
 
 /* user-visible error numbers are in the range -1 - -125: see <asm-sh64/errno.h> */
 



             reply	other threads:[~2005-08-10 20:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-10 20:13 Robert Love [this message]
2005-08-10 20:07 ` [patch] SH: inotify and ioprio syscalls Robert Love
2005-08-12  3:17   ` Paul Mundt

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=1123704797.23297.13.camel@betsy \
    --to=rlove@rlove.org \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ttb@tentacle.dhs.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