From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
Al Viro <viro@zeniv.linux.org.uk>,
Alexander Lobakin <alobakin@pm.me>,
Andrew Morton <akpm@linux-foundation.org>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Huacai Chen <chenhuacai@kernel.org>,
Jiaxun Yang <jiaxun.yang@flygoat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Randy Dunlap <rdunlap@infradead.org>,
Sean Christopherson <seanjc@google.com>
Subject: Re: [PATCH 1/2] mips: syscalls: switch to generic syscalltbl.sh
Date: Wed, 10 Mar 2021 16:07:05 +0100 [thread overview]
Message-ID: <20210310150705.GA12960@alpha.franken.de> (raw)
In-Reply-To: <20210301144825.357922-1-masahiroy@kernel.org>
On Mon, Mar 01, 2021 at 11:48:24PM +0900, Masahiro Yamada wrote:
> Many architectures duplicate similar shell scripts.
>
> This commit converts mips to use scripts/syscalltbl.sh. This also
> unifies syscall_table_32_o32.h and syscall_table_64_o32.h into
> syscall_table_o32.h.
>
> The offset parameters are unneeded here; __SYSCALL(nr, entry) is defined
> as 'PTR entry', so the parameter 'nr' is not used in the first place.
>
> With this commit, syscall tables and generated files are straight
> mapped, which makes things easier to understand.
>
> syscall_n32.tbl --> syscall_table_n32.h
> syscall_n64.tbl --> syscall_table_n64.h
> syscall_o32.tbl --> syscall_table_o32.h
>
> Then, the abi parameters are also unneeded.
>
> Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
> ---
>
> arch/mips/include/asm/Kbuild | 7 +++--
> arch/mips/kernel/scall32-o32.S | 4 +--
> arch/mips/kernel/scall64-n32.S | 3 +--
> arch/mips/kernel/scall64-n64.S | 3 +--
> arch/mips/kernel/scall64-o32.S | 4 +--
> arch/mips/kernel/syscalls/Makefile | 31 ++++++---------------
> arch/mips/kernel/syscalls/syscalltbl.sh | 36 -------------------------
> 7 files changed, 17 insertions(+), 71 deletions(-)
> delete mode 100644 arch/mips/kernel/syscalls/syscalltbl.sh
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 ]
prev parent reply other threads:[~2021-03-10 15:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-01 14:48 [PATCH 1/2] mips: syscalls: switch to generic syscalltbl.sh Masahiro Yamada
2021-03-01 14:48 ` [PATCH 2/2] mips: syscalls: switch to generic syscallhdr.sh Masahiro Yamada
2021-03-10 15:07 ` Thomas Bogendoerfer
2021-03-10 15:07 ` Thomas Bogendoerfer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210310150705.GA12960@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=akpm@linux-foundation.org \
--cc=alobakin@pm.me \
--cc=chenhuacai@kernel.org \
--cc=geert@linux-m68k.org \
--cc=jiaxun.yang@flygoat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=pbonzini@redhat.com \
--cc=rdunlap@infradead.org \
--cc=seanjc@google.com \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox