From: sashiko-bot@kernel.org
To: "André Almeida" <andrealmeid@igalia.com>
Cc: "Heiko Carstens" <hca@linux.ibm.com>,
"Vasily Gorbik" <gor@linux.ibm.com>,
"Christian Borntraeger" <borntraeger@linux.ibm.com>,
"Alexander Gordeev" <agordeev@linux.ibm.com>,
linux-s390@vger.kernel.org
Subject: Re: [PATCH v8 08/12] mips: Use the common syscall table
Date: Sat, 19 Sep 2026 00:54:35 +0000 [thread overview]
Message-ID: <20260919005436.2EE1E1F00898@smtp.kernel.org> (raw)
In-Reply-To: <20260918-tonyk-syscall_table-v8-8-0e2d60cad13e@igalia.com>
> Syscall numbers from 403 are shared with all architectures, so move the
> toolchain to use the common syscall table and remove duplicated code.
>
> The generated files are not exactly the same as before, but they have no
> functional changes:
>
> - For O32 ABI, the syscall table would have entries like
> __SYSCALL_WITH_COMPAT(403, sys_clock_gettime, sys_clock_gettime)
> which is equivalent to the new entry __SYSCALL(403, sys_clock_gettime)
>
> - For N32 ABI, the syscall table would have entries like
> __SYSCALL(413, compat_sys_pselect6_time64), which is equivalent to
> __SYSCALL_WITH_COMPAT(413, sys_pselect6, compat_sys_pselect6_time64)
> given the new __SYSCALL_WITH_COMPAT() definition for N32.
>
> - The above applies for N64 ABI as well.
>
> Signed-off-by: André Almeida <andrealmeid@igalia.com>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260918-tonyk-syscall_table-v8-0-0e2d60cad13e@igalia.com?part=8
next prev parent reply other threads:[~2026-09-19 0:54 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-19 0:31 [PATCH v8 00/12] syscalls: Add a shared table for all archs André Almeida
2026-09-19 0:31 ` [PATCH v8 01/12] syscalls: Make --abis parsing more robust André Almeida
2026-09-19 0:41 ` sashiko-bot
2026-09-19 0:31 ` [PATCH v8 02/12] syscalls: Create unified partial table for all archs André Almeida
2026-09-19 0:41 ` sashiko-bot
2026-09-19 0:31 ` [PATCH v8 03/12] scripts/syscall.tbl: Use the common table André Almeida
2026-09-19 0:41 ` sashiko-bot
2026-09-19 0:31 ` [PATCH v8 04/12] s390: Use the common syscall table André Almeida
2026-09-19 0:50 ` sashiko-bot
2026-09-19 0:31 ` [PATCH v8 05/12] sparc: " André Almeida
2026-09-19 0:45 ` sashiko-bot
2026-09-19 0:31 ` [PATCH v8 06/12] mips: Remove duplicated syscallnr.sh André Almeida
2026-09-19 0:45 ` sashiko-bot
2026-09-19 0:31 ` [PATCH v8 07/12] mips: Get rid of custom mips ABIs for syscall tables André Almeida
2026-09-19 0:52 ` sashiko-bot
2026-09-19 0:31 ` [PATCH v8 08/12] mips: Use the common syscall table André Almeida
2026-09-19 0:54 ` sashiko-bot [this message]
2026-09-19 0:31 ` [PATCH v8 09/12] syscalls: Add an option for offsetting the common table André Almeida
2026-09-19 0:55 ` sashiko-bot
2026-09-19 0:31 ` [PATCH v8 10/12] alpha: Define entry point for set_mempolicy_home_node syscall André Almeida
2026-09-19 0:55 ` sashiko-bot
2026-09-19 0:31 ` [PATCH v8 11/12] alpha: Remove alpha_ prefix from custom syscall entries André Almeida
2026-09-19 0:59 ` sashiko-bot
2026-09-19 0:31 ` [PATCH v8 12/12] alpha: Use the common syscall table André Almeida
2026-09-19 1:01 ` sashiko-bot
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=20260919005436.2EE1E1F00898@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=agordeev@linux.ibm.com \
--cc=andrealmeid@igalia.com \
--cc=borntraeger@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=linux-s390@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.