From: Daniel Jacobowitz <dan@debian.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: LKML <linux-kernel@vger.kernel.org>,
paulus@samba.org, anton@samba.org, davem@davemloft.net,
ralf@linux-mips.org, tony.luck@intel.com, ak@suse.de,
willy@debian.org, schwidefsky@de.ibm.com
Subject: Re: [PATCH] Consolidate compat_sys_waitid
Date: Tue, 15 Feb 2005 14:33:04 -0500 [thread overview]
Message-ID: <20050215193304.GA1175@nevyn.them.org> (raw)
In-Reply-To: <20050215140149.0b06c96b.sfr@canb.auug.org.au>
On Tue, Feb 15, 2005 at 02:01:49PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> This patch does:
> - consolidate the three implementations of compat_sys_waitid
> (some were called sys32_waitid).
> - adds sys_waitid syscall to ppc
> - adds sys_waitid and compat_sys_waitid syscalls to ppc64
>
> Parisc seemed to assume th existance of compat_sys_waitid. The MIPS
> syscall tables have me confused and may need updating. I have arbitrarily
> chosen the next available syscall number on ppc and ppc64, I hope this is
> correct.
I posted a (not-consolidated) sys32_waitid to the MIPS list on Sunday.
The syscall tables should confuse you :-) N32 needs to use compat
versions of most structures, but not siginfo_t. O32 needs to use
compat versions of everything. Your new version can replace the
sys32_waitid from my patch, but not sysn32_waitid.
Ralf, I'll let you sort it out :-)
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-02-15 19:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-15 3:01 [PATCH] Consolidate compat_sys_waitid Stephen Rothwell
2005-02-15 9:51 ` Andi Kleen
2005-02-15 11:06 ` Stephen Rothwell
2005-02-15 11:10 ` Andi Kleen
2005-02-15 18:37 ` David S. Miller
2005-02-15 18:43 ` Matthew Wilcox
2005-02-15 19:23 ` Andi Kleen
2005-02-15 19:27 ` Al Viro
2005-02-18 5:22 ` Stephen Rothwell
2005-02-15 19:33 ` Daniel Jacobowitz [this message]
2005-02-16 0:06 ` Paul Mackerras
-- strict thread matches above, loose matches on Subject: below --
2005-02-15 18:09 Luck, Tony
2005-03-07 1:08 Stephen Rothwell
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=20050215193304.GA1175@nevyn.them.org \
--to=dan@debian.org \
--cc=ak@suse.de \
--cc=anton@samba.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.org \
--cc=ralf@linux-mips.org \
--cc=schwidefsky@de.ibm.com \
--cc=sfr@canb.auug.org.au \
--cc=tony.luck@intel.com \
--cc=willy@debian.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