From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michal Simek Subject: Re: microblaze syscall list Date: Tue, 06 May 2008 10:33:07 +0200 Message-ID: <482017C3.2070508@seznam.cz> References: <87a5b0800804220513t75690ceao938a288596b5ad0c@mail.gmail.com> <4813DF3E.6080800@itee.uq.edu.au> <4814A153.3040600@seznam.cz> <200805032357.41043.arnd@arndb.de> <481D7DF7.3000909@seznam.cz> <481E3433.2030408@zytor.com> Reply-To: monstr@seznam.cz Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: Received: from smtp1.wifiinternet.cz ([89.31.47.1]:64095 "EHLO bor.wifiinternet.cz" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1753653AbYEFIcB (ORCPT ); Tue, 6 May 2008 04:32:01 -0400 In-Reply-To: <481E3433.2030408@zytor.com> Sender: linux-arch-owner@vger.kernel.org List-ID: To: "H. Peter Anvin" Cc: Arnd Bergmann , microblaze-uclinux@itee.uq.edu.au, Matthew Wilcox , Will Newton , Linux Kernel list , linux-arch@vger.kernel.org, git@xilinx.com, John Williams , Stephen Neuendorffer , John Linn Hi hpa, >> >> /* kernel/sys_ni.c */ >> .long sys_ni_syscall /* :-) */ >> > > There is a school of thought that it's useful to reserve a system call > number (usually zero) as a system call that is *guaranteed* to have no > effect. I like your opinion. I'll add it like zero syscall. Thanks, M