From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from moutng.kundenserver.de ([212.227.126.171]:30689 "EHLO moutng.kundenserver.de") by vger.kernel.org with ESMTP id S1750805AbWH3MjU (ORCPT ); Wed, 30 Aug 2006 08:39:20 -0400 From: Arnd Bergmann Subject: Re: [PATCH 4/7] Remove the use of _syscallX macros in UML Date: Wed, 30 Aug 2006 14:38:41 +0200 References: <20060827214734.252316000@klappe.arndb.de> <20060827215636.797086000@klappe.arndb.de> <44F524EE.90304@zytor.com> In-Reply-To: <44F524EE.90304@zytor.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200608301438.42079.arnd@arndb.de> Sender: linux-arch-owner@vger.kernel.org To: "H. Peter Anvin" Cc: linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org, Jeff Dike , Bjoern Steinbrink , Arjan van de Ven , Chase Venters , Andrew Morton , Russell King , rusty@rustcorp.com.au List-ID: On Wednesday 30 August 2006 07:41, H. Peter Anvin wrote: > syscall() is a horrible botch; it is in fact unimplementable (without > enormous switch statements) on a number of architectures. > Ok, good point. I'll leave the _syscallX() macros in for now and only remove the kernel syscalls in my next submission, so we get at least the non-controversial part done. Arnd <><