From: "Kip Walker" <kwalker@broadcom.com>
To: "Ralf Baechle" <ralf@linux-mips.org>, linux-mips@linux-mips.org
Subject: mips64 scall_o32.S fixes?
Date: Fri, 07 Mar 2003 11:27:45 -0800 [thread overview]
Message-ID: <3E68F2B1.3413093D@broadcom.com> (raw)
I assume sys32_syscall should only allow o32 syscalls? So the #defines
being used were wrong. And MAX_SYSCALL_NO, although unused, seems to
have the wrong thing in it.
Any disagreement?
Kip
Index: arch/mips64/kernel/scall_o32.S
===================================================================
RCS file: /home/cvs/linux/arch/mips64/kernel/scall_o32.S,v
retrieving revision 1.48.2.26
diff -u -r1.48.2.26 scall_o32.S
--- arch/mips64/kernel/scall_o32.S 7 Mar 2003 01:22:48 -0000
1.48.2.26
+++ arch/mips64/kernel/scall_o32.S 7 Mar 2003 19:26:36 -0000
@@ -23,7 +23,7 @@
#include <asm/sysmips.h>
/* Highest syscall used of any syscall flavour */
-#define MAX_SYSCALL_NO __NR_Linux32 + __NR_Linux32_syscalls
+#define MAX_SYSCALL_NO __NR_N32_Linux + __NR_N32_Linux_syscalls
.align 5
NESTED(handle_sys, PT_SIZE, sp)
@@ -263,7 +263,7 @@
LEAF(sys32_syscall)
ld t0, PT_R29(sp) # user sp
- sltu v0, a0, __NR_Linux + __NR_Linux_syscalls + 1
+ sltu v0, a0, __NR_O32_Linux + __NR_O32_Linux_syscalls + 1
beqz v0, enosys
dsll v0, a0, 3
reply other threads:[~2003-03-07 19:38 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=3E68F2B1.3413093D@broadcom.com \
--to=kwalker@broadcom.com \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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