From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: Andi Kleen <ak@suse.de>
Cc: Andrew Morton <akpm@osdl.org>, linux-arch@vger.kernel.org
Subject: Re: new syscalls
Date: Fri, 20 Jan 2006 10:43:09 +0100 [thread overview]
Message-ID: <20060120094309.GA9349@osiris.boeblingen.de.ibm.com> (raw)
In-Reply-To: <200601180438.03957.ak@suse.de>
> > Verious new syscalls which are trickling their way Linuswards and will need
> > testing and wiring up once they get there:
> >
> > sys_migrate_pages
> > Merged
>
> #define __NR_migrate_pages 256
> __SYSCALL(__NR_migrate_pages, sys_migrate_pages)
>
>
> We first have to wait if everybody survived crossing the 8bit boundary @)
Any reason why arch/x86_64/ia32/ia32entry.S has sys_futimesat in its syscall
table instead of compat_sys_futimesat? Looks wrong to me...
Thanks,
Heiko
next prev parent reply other threads:[~2006-01-20 9:44 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-18 3:29 new syscalls Andrew Morton
2006-01-18 3:38 ` Andi Kleen
2006-01-20 9:43 ` Heiko Carstens [this message]
2006-01-20 9:48 ` Andi Kleen
2006-01-20 9:49 ` David S. Miller
-- strict thread matches above, loose matches on Subject: below --
2006-01-18 18:55 Luck, Tony
2006-01-18 21:36 ` Andrew Morton
2006-01-18 21:48 ` Ulrich Drepper
2006-01-18 21:58 ` David S. Miller
2006-01-18 21:53 ` David Woodhouse
2006-01-18 21:58 ` David S. Miller
2006-01-20 10:04 ` Andi Kleen
2006-01-20 10:15 ` David S. Miller
2006-01-23 6:44 ` David Woodhouse
2006-01-23 9:58 ` Heiko Carstens
2006-01-19 1:17 ` Davide Libenzi
2006-01-19 1:26 ` David S. Miller
2006-01-19 5:00 ` David Woodhouse
2006-01-19 1:28 ` Andrew Morton
2006-01-19 21:48 ` Davide Libenzi
2006-01-20 0:13 ` Davide Libenzi
2006-01-20 0:23 ` Ulrich Drepper
2006-01-20 0:34 ` Davide Libenzi
2006-01-19 1:19 ` Christoph Lameter
2006-01-19 2:30 ` Andi Kleen
2006-01-19 13:50 ` JANAK DESAI
2006-01-22 17:45 ` JANAK DESAI
2006-01-24 23:44 ` JANAK DESAI
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=20060120094309.GA9349@osiris.boeblingen.de.ibm.com \
--to=heiko.carstens@de.ibm.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=linux-arch@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