From: Andi Kleen <ak@suse.de>
To: David Howells <dhowells@redhat.com>
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: [PATCH] Add key management syscalls to non-i386 archs
Date: 20 Oct 2004 21:25:35 +0200 [thread overview]
Message-ID: <p73d5zdyyxc.fsf@verdi.suse.de> (raw)
In-Reply-To: <3506.1098283455@redhat.com.suse.lists.linux.kernel>
David Howells <dhowells@redhat.com> writes:
> /* Syscall protocol:
> diff -uNrp linux-2.6.9-bk4/include/asm-x86_64/unistd.h linux-2.6.9-bk4-keys/include/asm-x86_64/unistd.h
> --- linux-2.6.9-bk4/include/asm-x86_64/unistd.h 2004-10-19 10:42:16.000000000 +0100
> +++ linux-2.6.9-bk4-keys/include/asm-x86_64/unistd.h 2004-10-20 14:06:01.645026869 +0100
> @@ -556,8 +556,14 @@ __SYSCALL(__NR_mq_getsetattr, sys_mq_get
> __SYSCALL(__NR_kexec_load, sys_ni_syscall)
> #define __NR_waitid 247
> __SYSCALL(__NR_waitid, sys_waitid)
> +#define __NR_add_key 248
> +__SYSCALL(__NR_add_key, sys_add_key)
Hey, I already allocated 248 for setaltroot. And no, you cannot
allocate system calls on your own without going through the
architecture maintainer. The normal workflow is that you add
them to i386 and the other follow on their own.
Andrew, please don't apply the x86-64 parts of this.
-Andi
next parent reply other threads:[~2004-10-20 19:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3506.1098283455@redhat.com.suse.lists.linux.kernel>
2004-10-20 19:25 ` Andi Kleen [this message]
2004-10-20 19:48 ` [PATCH] Add key management syscalls to non-i386 archs David Howells
2004-10-20 20:22 ` Andrew Morton
2004-10-21 9:20 ` Arjan van de Ven
2004-10-20 14:44 David Howells
2004-10-20 15:29 ` Christoph Hellwig
2004-10-20 17:50 ` Andrew Morton
2004-10-20 18:18 ` Christoph Hellwig
2004-10-20 16:42 ` Geert Uytterhoeven
2004-10-20 17:08 ` Arnd Bergmann
2004-10-20 22:01 ` David S. Miller
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=p73d5zdyyxc.fsf@verdi.suse.de \
--to=ak@suse.de \
--cc=akpm@osdl.org \
--cc=dhowells@redhat.com \
--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