Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S267619AbUJTW74 (ORCPT ); Wed, 20 Oct 2004 18:59:56 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S270482AbUJTWdg (ORCPT ); Wed, 20 Oct 2004 18:33:36 -0400 Received: from mx1.redhat.com ([66.187.233.31]:48790 "EHLO mx1.redhat.com") by vger.kernel.org with ESMTP id S269112AbUJTTsi (ORCPT ); Wed, 20 Oct 2004 15:48:38 -0400 From: David Howells In-Reply-To: References: <3506.1098283455@redhat.com.suse.lists.linux.kernel> To: Andi Kleen Cc: linux-kernel@vger.kernel.org, akpm@osdl.org Subject: Re: [PATCH] Add key management syscalls to non-i386 archs User-Agent: EMH/1.14.1 SEMI/1.14.5 (Awara-Onsen) FLIM/1.14.5 (Demachiyanagi) APEL/10.6 Emacs/21.3 (i386-redhat-linux-gnu) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen") Content-Type: text/plain; charset=US-ASCII Date: Wed, 20 Oct 2004 20:48:16 +0100 Message-ID: <23586.1098301696@redhat.com> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 617 Lines: 14 > 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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/