[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAK8P3a2CqpjG4b9WNYwi5-B8=RHN+edji0p5_Y3Ln-oH_B-Auw@mail.gmail.com>
Date: Wed, 9 Jan 2019 11:10:42 +0100
From: Arnd Bergmann <arnd@...db.de>
To: Firoz Khan <firoz.khan@...aro.org>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Philippe Ombredanne <pombredanne@...b.com>,
Thomas Gleixner <tglx@...utronix.de>,
Kate Stewart <kstewart@...uxfoundation.org>,
y2038 Mailman List <y2038@...ts.linaro.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
linux-arch <linux-arch@...r.kernel.org>,
Deepa Dinamani <deepa.kernel@...il.com>,
Marcin Juszkiewicz <marcin.juszkiewicz@...aro.org>
Subject: Re: [PATCH v2] scripts/syscalls: add system call table file for asm-generic
On Mon, Jan 7, 2019 at 3:31 PM Firoz Khan <firoz.khan@...aro.org> wrote:
> +242 common accept4 sys_accept4
> +243 common recvmmsg sys_recvmmsg compat_sys_recvmmsg
> +244 archs0 arch_specific_syscall0 sys_arch_specific_syscall0
> +245 archs1 arch_specific_syscall1 sys_arch_specific_syscall1
> +246 archs2 arch_specific_syscall2 sys_arch_specific_syscall2
> +247 archs3 arch_specific_syscall3 sys_arch_specific_syscall3
> +248 archs4 arch_specific_syscall4 sys_arch_specific_syscall4
> +260 common wait4 sys_wait4 compat_sys_wait4
This arch_specific_syscall0 should be fine as well, but there is a small
chance that existing user space code refers to the __NR_arch_specific_syscall
(without trailing 0) macro, so please change 244 back to
'arch_specific_syscall'.
Not sure if we should then count from 0 or 1, i.e. whether 245 should be
arch_specific_syscall1 or arch_specific_syscall2.
Arnd
Powered by blists - more mailing lists