[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210601094753.GC6961@alpha.franken.de>
Date: Tue, 1 Jun 2021 11:47:53 +0200
From: Thomas Bogendoerfer <tsbogend@...ha.franken.de>
To: Masahiro Yamada <masahiroy@...nel.org>
Cc: linux-mips@...r.kernel.org, linux-kernel@...r.kernel.org,
Alexander Lobakin <alobakin@...me>,
Geert Uytterhoeven <geert@...ux-m68k.org>
Subject: Re: [PATCH 1/2] mips: syscalls: define syscall offsets directly in
<asm/unistd.h>
On Fri, May 28, 2021 at 12:46:14PM +0900, Masahiro Yamada wrote:
> There is no good reason to generate the syscall offset macros by
> scripting since they are not derived from the syscall tables.
>
> Define __NR_*_Linux macros directly in arch/mips/include/asm/unistd.h,
> and clean up the Makefile and the shell script.
>
> Signed-off-by: Masahiro Yamada <masahiroy@...nel.org>
> ---
>
> arch/mips/include/asm/unistd.h | 4 ++++
> arch/mips/kernel/syscalls/Makefile | 6 +-----
> arch/mips/kernel/syscalls/syscallnr.sh | 2 --
> 3 files changed, 5 insertions(+), 7 deletions(-)
applied to mips-next.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
Powered by blists - more mailing lists