public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: akpm@osdl.org
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH 1/2] adjust parisc sys_ptrace prototype
Date: Mon, 26 Sep 2005 14:37:50 +0200	[thread overview]
Message-ID: <20050926123750.GA25496@lst.de> (raw)

Make the pid argument a long as on every other arcihtecture.  Despite
pid_t beeing a 32bit type even on 64bit parisc this is not an ABI change
due to the parisc calling conventions.  And even if it did it wouldn't
matter too much because 64bit userspace on parisc is in an embrionic
stage.

Acked-by: Matthew Wilcox <matthew@wil.cx>
Signed-off-by: Christoph Hellwig <hch@lst.de>

Index: linux-2.6/arch/parisc/kernel/ptrace.c
===================================================================
--- linux-2.6.orig/arch/parisc/kernel/ptrace.c	2005-09-20 23:57:49.000000000 +0200
+++ linux-2.6/arch/parisc/kernel/ptrace.c	2005-09-21 11:31:34.000000000 +0200
@@ -78,7 +78,7 @@
 	pa_psw(child)->l = 0;
 }
 
-long sys_ptrace(long request, pid_t pid, long addr, long data)
+long sys_ptrace(long request, long pid, long addr, long data)
 {
 	struct task_struct *child;
 	long ret;
Index: linux-2.6/include/asm-parisc/unistd.h
===================================================================
--- linux-2.6.orig/include/asm-parisc/unistd.h	2005-09-20 23:57:49.000000000 +0200
+++ linux-2.6/include/asm-parisc/unistd.h	2005-09-21 11:35:23.000000000 +0200
@@ -1005,7 +1005,6 @@
 		struct pt_regs *regs);
 int sys_vfork(struct pt_regs *regs);
 int sys_pipe(int *fildes);
-long sys_ptrace(long request, pid_t pid, long addr, long data);
 struct sigaction;
 asmlinkage long sys_rt_sigaction(int sig,
 				const struct sigaction __user *act,


                 reply	other threads:[~2005-09-26 12:37 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=20050926123750.GA25496@lst.de \
    --to=hch@lst.de \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.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