All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <randy.dunlap@verizon.net>
To: Andrew Morton <akpm@digeo.com>
Cc: Linux-kernel@vger.kernel.org, torvalds@transmeta.com, ak@suse.de,
	rml@tech9.net
Subject: Re: [PATCH] arch-independent syscalls to return long
Date: Thu, 20 Mar 2003 22:39:11 -0800	[thread overview]
Message-ID: <3E7AB38F.124B98E4@verizon.net> (raw)
In-Reply-To: 20030320222358.454a1f4f.akpm@digeo.com

Andrew Morton wrote:
> 
> "Randy.Dunlap" <randy.dunlap@verizon.net> wrote:
> >
> > Hi,
> >
> > I posted this about 1 month ago (as [RFC]), to no avail.
> > However, tonight Andi needs it for pause() [which is failing
> > on x86_64], and Robert Love mentioned converting the affinity
> > syscalls.  I had already done them, so here they are again.
> >
> 
> Thanks.  Is that all of them done now?

AFAIK, without guarantees.  I used a list from Jamie Lokier and then
went thru bunches of source files & syscalls myself and came up with
these.

There are still some syscall prototypes that are declared as int
instead of long, but I can't fix them tonight (zzz).  Examples:

	sys_sched_setaffinity
		arch/sparc64/, arch/ppc64/, arch/s390x/ (FIX PROTO)
	sys_sched_getaffinity
		arch/sparc64/, arch/ppc64/, arch/s390x/ (FIX PROTO)
	sys_remap_file_pages
		arch/sparc/ (FIX PROTO)
	sys_lookup_dcookie
		arch/sparc64/, arch/ppc64/, arch/parisc/ (FIX PROTO)


That's all that I know of.

~Randy

  reply	other threads:[~2003-03-21  6:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-21  6:11 [PATCH] arch-independent syscalls to return long Randy.Dunlap
2003-03-21  6:23 ` Andrew Morton
2003-03-21  6:39   ` Randy.Dunlap [this message]
2003-03-21  6:51   ` Robert Love
2003-03-21 18:46     ` Randy.Dunlap
2003-03-21 19:23       ` Robert Love
2003-03-21 19:28         ` Robert Love

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=3E7AB38F.124B98E4@verizon.net \
    --to=randy.dunlap@verizon.net \
    --cc=Linux-kernel@vger.kernel.org \
    --cc=ak@suse.de \
    --cc=akpm@digeo.com \
    --cc=rml@tech9.net \
    --cc=torvalds@transmeta.com \
    /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.