public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Love <rml@novell.com>
To: Andrew Morton <akpm@osdl.org>
Cc: paulus@samba.org, linux-kernel@vger.kernel.org, ttb@tentacle.dhs.org
Subject: [patch] inotify: ppc64 syscalls.
Date: Wed, 27 Jul 2005 13:31:36 -0400	[thread overview]
Message-ID: <1122485496.21253.170.camel@betsy> (raw)
In-Reply-To: <20050727095539.602fcc4a.akpm@osdl.org>

On Wed, 2005-07-27 at 09:55 -0700, Andrew Morton wrote:

> ppc64 likes to keep its 32-bit-syscall table in sync with ppc32 so it'd be
> best to do ppc64 while we're at it (both sys_call_table and
> sys_call_table32)

Sure thing.

Attached find inotify system call support for PPC64.

[ I don't think we need sys32 compatibility versions--and if we do, I
failed in life. ]

	Robert Love

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

 arch/ppc64/kernel/misc.S   |    6 ++++++
 include/asm-ppc64/unistd.h |    5 ++++-
 2 files changed, 10 insertions(+), 1 deletion(-)

diff -urN linux-2.6.13-rc3-git8/arch/ppc64/kernel/misc.S linux/arch/ppc64/kernel/misc.S
--- linux-2.6.13-rc3-git8/arch/ppc64/kernel/misc.S	2005-07-27 10:59:31.000000000 -0400
+++ linux/arch/ppc64/kernel/misc.S	2005-07-27 13:26:36.000000000 -0400
@@ -1129,6 +1129,9 @@
 	.llong .compat_sys_waitid
 	.llong .sys32_ioprio_set
 	.llong .sys32_ioprio_get
+	.llong .sys_inotify_init	/* 275 */
+	.llong .sys_inotify_add_watch
+	.llong .sys_inotify_rm_watch
 
 	.balign 8
 _GLOBAL(sys_call_table)
@@ -1407,3 +1410,6 @@
 	.llong .sys_waitid
 	.llong .sys_ioprio_set
 	.llong .sys_ioprio_get
+	.llong .sys_inotify_init	/* 275 */
+	.llong .sys_inotify_add_watch
+	.llong .sys_inotify_rm_watch
diff -urN linux-2.6.13-rc3-git8/include/asm-ppc64/unistd.h linux/include/asm-ppc64/unistd.h
--- linux-2.6.13-rc3-git8/include/asm-ppc64/unistd.h	2005-07-27 10:59:32.000000000 -0400
+++ linux/include/asm-ppc64/unistd.h	2005-07-27 13:27:24.000000000 -0400
@@ -285,8 +285,11 @@
 #define __NR_waitid		272
 #define __NR_ioprio_set		273
 #define __NR_ioprio_get		274
+#define __NR_inotify_init	275
+#define __NR_inotify_add_watch	276
+#define __NR_inotify_rm_watch	277
 
-#define __NR_syscalls		275
+#define __NR_syscalls		278
 #ifdef __KERNEL__
 #define NR_syscalls	__NR_syscalls
 #endif



  reply	other threads:[~2005-07-27 17:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-27 15:45 [patch] inotify: ppc32 syscalls Robert Love
2005-07-27 16:55 ` Andrew Morton
2005-07-27 17:31   ` Robert Love [this message]
2005-07-27 20:27     ` [patch] inotify: ppc64 syscalls David S. Miller
2005-07-27 20:31       ` Robert Love
2005-07-27 20:33         ` David S. Miller

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=1122485496.21253.170.camel@betsy \
    --to=rml@novell.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulus@samba.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