From: David Howells <dhowells@redhat.com>
To: Andi Kleen <ak@suse.de>
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: [PATCH] Add key management syscalls to non-i386 archs
Date: Wed, 20 Oct 2004 20:48:16 +0100 [thread overview]
Message-ID: <23586.1098301696@redhat.com> (raw)
In-Reply-To: <p73d5zdyyxc.fsf@verdi.suse.de>
> 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.
That's what I intended, but others, especially Arjan, seem to think I should
do all the compat stuff for all archs myself.
David
next prev parent reply other threads:[~2004-10-20 22:59 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 ` [PATCH] Add key management syscalls to non-i386 archs Andi Kleen
2004-10-20 19:48 ` David Howells [this message]
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=23586.1098301696@redhat.com \
--to=dhowells@redhat.com \
--cc=ak@suse.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