From: Borislav Deianov <borislav@lix.polytechnique.fr>
To: linuxppc-dev@lists.linuxppc.org
Subject: [2.3.35] syscall 190 on ppc (fwd)
Date: Fri, 7 Jan 2000 02:03:36 +0200 [thread overview]
Message-ID: <20000107020336.B569@wispa.polytechnique.fr> (raw)
[-- Attachment #1: Type: text/plain, Size: 565 bytes --]
Hi,
I posted the message below to linux-kernel but was advised to repost
it here as well.
Best wishes,
Borislav
----- Forwarded message from borislav -----
Date: Wed, 29 Dec 1999 22:57:01 +0200
To: Cort Dougan <cort@fsmlabs.com>
Cc: linux-kernel@vger.rutgers.edu
Subject: [2.3.35] syscall 190 on ppc
Hi,
According to include/asm-ppc/unistd.h, ugetrlimit on ppc is number 191
but in arch/ppc/kernel/misc.S sys_getrlimit is number 190. Looks like
190 was omitted in unistd.h. Patch against 2.3.35 attached.
Regards,
Borislav
----- End forwarded message -----
[-- Attachment #2: ppc-190.patch --]
[-- Type: text/plain, Size: 790 bytes --]
--- linux-2.3.35/include/asm-ppc/unistd.h~ Wed Dec 29 14:53:42 1999
+++ linux-2.3.35/include/asm-ppc/unistd.h Wed Dec 29 21:31:35 1999
@@ -194,13 +194,13 @@
#define __NR_getpmsg 187 /* some people actually want streams */
#define __NR_putpmsg 188 /* some people actually want streams */
#define __NR_vfork 189
-#define __NR_ugetrlimit 191 /* SuS compliant getrlimit */
-#define __NR_mmap2 192
-#define __NR_truncate64 193
-#define __NR_ftruncate64 194
-#define __NR_stat64 195
-#define __NR_lstat64 196
-#define __NR_fstat64 197
+#define __NR_ugetrlimit 190 /* SuS compliant getrlimit */
+#define __NR_mmap2 191
+#define __NR_truncate64 192
+#define __NR_ftruncate64 193
+#define __NR_stat64 194
+#define __NR_lstat64 195
+#define __NR_fstat64 196
#define __NR(n) #n
reply other threads:[~2000-01-07 0:03 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=20000107020336.B569@wispa.polytechnique.fr \
--to=borislav@lix.polytechnique.fr \
--cc=linuxppc-dev@lists.linuxppc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.