From: Nicolas Schier <nsc@kernel.org>
To: "Arnd Bergmann" <arnd@arndb.de>,
"Thomas Bogendoerfer" <tsbogend@alpha.franken.de>,
"Nathan Chancellor" <nathan@kernel.org>,
"Thomas Weißschuh" <linux@weissschuh.net>
Cc: linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mips@vger.kernel.org, linux-kbuild@vger.kernel.org
Subject: Re: [PATCH v3 0/3] checksyscalls: only run when necessary
Date: Thu, 02 Apr 2026 22:20:40 +0200 [thread overview]
Message-ID: <177516124052.3536083.11423413906699581332.b4-ty@b4> (raw)
In-Reply-To: <20260402-kbuild-missing-syscalls-v3-0-6641be1de2db@weissschuh.net>
On Thu, 02 Apr 2026 16:36:17 +0200, Thomas Weißschuh wrote:
> checksyscalls: only run when necessary
>
> 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.
>
> [...]
Applied to kbuild/linux.git (kbuild-next-unstable), thanks!
[1/3] checksyscalls: move path to reference table to a variable
https://git.kernel.org/kbuild/c/263246f2
[2/3] checksyscalls: only run when necessary
https://git.kernel.org/kbuild/c/a414e4ba
[3/3] checksyscalls: move instance functionality into generic code
https://git.kernel.org/kbuild/c/a46f42c3
Please look out for regression or issue reports or other follow up
comments, as they may result in the patch/series getting dropped,
reverted or modified (e.g. trailers). Patches applied to the
kbuild-next-unstable branch are accepted pending wider testing in
linux-next and any post-commit review; they will generally be moved
to the kbuild-next branch in about a week if no issues are found.
Best regards,
--
Nicolas
prev parent reply other threads:[~2026-04-02 20:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-02 14:36 [PATCH v3 0/3] checksyscalls: only run when necessary Thomas Weißschuh
2026-04-02 14:36 ` [PATCH v3 1/3] checksyscalls: move path to reference table to a variable Thomas Weißschuh
2026-04-02 14:36 ` [PATCH v3 2/3] checksyscalls: only run when necessary Thomas Weißschuh
2026-04-02 14:36 ` [PATCH v3 3/3] checksyscalls: move instance functionality into generic code Thomas Weißschuh
2026-04-02 20:20 ` Nicolas Schier [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=177516124052.3536083.11423413906699581332.b4-ty@b4 \
--to=nsc@kernel.org \
--cc=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=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).