From: "David S. Miller" <davem@davemloft.net>
To: Andi Kleen <ak@suse.de>
Cc: dhowells@redhat.com, torvalds@osdl.org, akpm@osdl.org,
linux-kernel@vger.kernel.org, discuss@x86-64.org,
sparclinux@vger.kernel.org, linuxppc64-dev@ozlabs.org,
linux-m68k@vger.kernel.org, linux-sh@m17n.org,
linux-arm-kernel@lists.arm.linux.org.uk,
parisc-linux@parisc-linux.org, linux-ia64@vger.kernel.org,
linux-390@vm.marist.edu, linux-mips@linux-mips.org
Subject: Re: [discuss] Re: [PATCH] Add key management syscalls to non-i386
Date: Wed, 20 Oct 2004 23:04:50 +0000 [thread overview]
Message-ID: <20041020160450.0914270b.davem@davemloft.net> (raw)
In-Reply-To: <20041020225625.GD995@wotan.suse.de>
On Thu, 21 Oct 2004 00:56:25 +0200
Andi Kleen <ak@suse.de> wrote:
> I don't think that's a good idea. Normally new system calls
> are relatively obscure and the system works fine without them,
> so urgent action is not needed.
>
> And I think we can trust architecture maintainers to regularly
> sync the system calls with i386.
I disagree quite strongly. One major frustration for users of
non-x86 platforms is that functionality is often missing for some
time that we can make trivial to keep in sync.
I religiously watch what goes into Linus's tree for this purpose,
but that is kind of a rediculious burdon to expect every platform
maintainer to do. It's not just system calls, we have signal handling
bug fixes, trap handling infrastructure, and now the nice generic
IRQ handling subsystem as other examples.
Simply put, if you're not watching the tree in painstaking detail
every day, you miss all of these enhancements.
The knowledge should come from the person putting the changes into
the tree, therefore it gets done once and this makes it so that
the other platform maintainers will find out about it automatically
next time they update their tree.
next prev parent reply other threads:[~2004-10-20 23:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-20 14:44 [PATCH] Add key management syscalls to non-i386 archs 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 15:49 ` [parisc-linux] " Matthew Wilcox
2004-10-20 16:16 ` David Howells
2004-10-20 17:08 ` Arnd Bergmann
2004-10-20 22:01 ` David S. Miller
2004-10-20 22:56 ` [discuss] " Andi Kleen
2004-10-20 23:04 ` David S. Miller [this message]
2004-10-20 23:25 ` Andi Kleen
2004-10-20 23:41 ` [discuss] Re: [PATCH] Add key management syscalls to non-i386 David S. Miller
2004-10-21 0:10 ` [discuss] Re: [PATCH] Add key management syscalls to non-i386 archs Andi Kleen
2004-10-21 8:03 ` [discuss] Re: [PATCH] Add key management syscalls to non-i386 Geert Uytterhoeven
2004-10-21 1:55 ` Benjamin Herrenschmidt
2004-10-21 8:47 ` [discuss] Re: [PATCH] Add key management syscalls to non-i386 archs Jan-Benedict Glaw
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=20041020160450.0914270b.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=dhowells@redhat.com \
--cc=discuss@x86-64.org \
--cc=linux-390@vm.marist.edu \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-sh@m17n.org \
--cc=linuxppc64-dev@ozlabs.org \
--cc=parisc-linux@parisc-linux.org \
--cc=sparclinux@vger.kernel.org \
--cc=torvalds@osdl.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