From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from verein.lst.de (verein.lst.de [213.95.11.210]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTPS id 2D98F101F28 for ; Wed, 23 Jun 2010 20:14:28 +1000 (EST) Date: Wed, 23 Jun 2010 12:14:02 +0200 From: Christoph Hellwig To: Ian Munsie Subject: Re: [PATCH 12/40] x86, compat: convert ia32 layer to use Message-ID: <20100623101402.GA10564@lst.de> References: <1277287401-28571-1-git-send-email-imunsie@au1.ibm.com> <1277287401-28571-13-git-send-email-imunsie@au1.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <1277287401-28571-13-git-send-email-imunsie@au1.ibm.com> Cc: Andrew Morton , Frederic Weisbecker , Jason Baron , x86@kernel.org, Greg Ungerer , linux-kernel@vger.kernel.org, Steven Rostedt , linuxppc-dev@ozlabs.org, Ingo Molnar , Paul Mackerras , "H. Peter Anvin" , Russell King , Thomas Gleixner , Christoph Hellwig List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Any reason we need to differenciate between COMPAT_SYSCALL_DEFINE and ARCH_COMPAT_SYSCALL_DEFINE? We don't need this for native system calls, so I can't see the reason to do it for compat system calls.