From: "Arnd Bergmann" <arnd@arndb.de>
To: "Thomas Weißschuh" <linux@weissschuh.net>,
"Thomas Bogendoerfer" <tsbogend@alpha.franken.de>,
"Nathan Chancellor" <nathan@kernel.org>,
"Nicolas Schier" <nsc@kernel.org>
Cc: Linux-Arch <linux-arch@vger.kernel.org>,
linux-kernel@vger.kernel.org, linux-mips@vger.kernel.org,
linux-kbuild@vger.kernel.org
Subject: Re: [PATCH v2 0/3] checksyscalls: only run when necessary
Date: Tue, 24 Mar 2026 18:29:13 +0100 [thread overview]
Message-ID: <604e8db2-6745-48b1-9db7-29fe12eb9579@app.fastmail.com> (raw)
In-Reply-To: <20260324-kbuild-missing-syscalls-v2-0-651b8beb0bfd@weissschuh.net>
On Tue, Mar 24, 2026, at 18:16, Thomas Weißschuh wrote:
> Currently checksyscalls.sh is unconditionally executed during each build.
> Most of these executions are unnecessary.
>
> Only run checksyscalls.sh if one of its inputs have changed.
>
> Signed-off-by: Thomas Weißschuh <linux@weissschuh.net>
Nice series!
Acked-by: Arnd Bergmann <arnd@arndb.de>
At some point, we should revisit the syscall table use and just have
a shared table across all architectures for the syscalls above 402,
which are almost identical already. That requires a bit of scripting
but will let us just drop the checksyscalls script that hasn't
been all that useful for a while now.
Arnd
next prev parent reply other threads:[~2026-03-24 17:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-24 17:16 [PATCH v2 0/3] checksyscalls: only run when necessary Thomas Weißschuh
2026-03-24 17:16 ` [PATCH v2 1/3] checksyscalls: move path to reference table to a variable Thomas Weißschuh
2026-03-24 17:16 ` [PATCH v2 2/3] checksyscalls: only run when necessary Thomas Weißschuh
2026-03-24 17:16 ` [PATCH v2 3/3] checksyscalls: move instance functionality into generic code Thomas Weißschuh
2026-04-02 14:18 ` Nicolas Schier
2026-03-24 17:29 ` Arnd Bergmann [this message]
2026-04-02 14:18 ` [PATCH v2 0/3] checksyscalls: only run when necessary Nicolas Schier
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=604e8db2-6745-48b1-9db7-29fe12eb9579@app.fastmail.com \
--to=arnd@arndb.de \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=nathan@kernel.org \
--cc=nsc@kernel.org \
--cc=tsbogend@alpha.franken.de \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).