Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752122Ab2J0VIn (ORCPT ); Sat, 27 Oct 2012 17:08:43 -0400 Received: from mail-pb0-f46.google.com ([209.85.160.46]:55730 "EHLO mail-pb0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751382Ab2J0VIl (ORCPT ); Sat, 27 Oct 2012 17:08:41 -0400 Message-ID: <508C4D56.5030801@zankel.net> Date: Sat, 27 Oct 2012 14:08:38 -0700 From: Chris Zankel User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121011 Thunderbird/16.0.1 MIME-Version: 1.0 To: Ben Hutchings CC: linux-kernel@vger.kernel.org, stable@vger.kernel.org, alan@lxorguk.ukuu.org.uk, Greg Kroah-Hartman Subject: Re: [ 60/85] xtensa: add missing system calls to the syscall table References: <20121026000031.107227138@linuxfoundation.org> <20121026000037.158689095@linuxfoundation.org> <1351362392.4834.17.camel@deadeye.wl.decadent.org.uk> In-Reply-To: <1351362392.4834.17.camel@deadeye.wl.decadent.org.uk> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 954 Lines: 30 Hi Ben, On 10/27/2012 11:26 AM, Ben Hutchings wrote: > On Thu, 2012-10-25 at 17:06 -0700, Greg Kroah-Hartman wrote: > [...] >> #define __NR_available287 287 >> -__SYSCALL(287, sys_faccessat, 0) >> +__SYSCALL(287, sys_ni_syscall, 0) > [...] > > Why was this one un-plumbed rather than properly numbered (#define > __NR_faccessat)? I can only speculate, that this was probably a copy/paste error that has been there for a long time. __NR_faccessat is (and was) defined as number 301. Given that 287 was never defined, it's save to fix the table entry and set it to sys_ni_syscall. unistd.h: [...] #define __NR_faccessat 301 __SYSCALL(301, sys_faccessat, 4) [...] Thanks, -Chris -- 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/