From: Luis Augenstein <luis.augenstein@tngtech.com>
To: Nathan Chancellor <nathan@kernel.org>
Cc: nsc@kernel.org, linux-kbuild@vger.kernel.org,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
gregkh@linuxfoundation.org, kstewart@linuxfoundation.org,
maximilian.huber@tngtech.com
Subject: Re: [PATCH 1/1] kbuild: record real-prereqs in .cmd files
Date: Fri, 21 Aug 2026 21:57:03 +0200 [thread overview]
Message-ID: <1efb52b4-1a78-4c4e-aea1-6c8b426a8538@tngtech.com> (raw)
In-Reply-To: <178708267641.2113250.8208366109143651745.b4-review@b4>
[-- Attachment #1.1: Type: text/plain, Size: 1686 bytes --]
On 8/18/26 21:51, Nathan Chancellor wrote:
> Sashiko has a comment that this produces different results based on a
> clean versus incremental build:
>
> https://sashiko.dev/#/patchset/59032
>
> I can reproduce this with:
>
> $ make -skj"$(nproc)" ARCH=x86_64 mrproper defconfig lib/oid_registry.o
>
> $ grep -n oid_registry_data lib/.oid_registry.o.cmd
> 3:make_prereqs_lib/oid_registry.o := lib/oid_registry.c lib/oid_registry_data.c
> 1111: lib/oid_registry_data.c \
>
> $ touch lib/oid_registry.c
>
> $ make -skj"$(nproc)" ARCH=x86_64 lib/oid_registry.o
>
> $ grep -n oid_registry_data lib/.oid_registry.o.cmd
> 1111: lib/oid_registry_data.c \
>
> As this is just metadata for external tools (i.e., it does not get
> consumed by Kbuild again), we could just require them to filter
> duplicates after the fact?
True, some Make prerequisites also appear in deps_*, so the filter
dropped them from make_prereqs_* on incremental builds.
However, we cannot just remove the filter. After the .cmd is included,
$(real-prereqs) contains $(deps_$@), so the whole deps_* list would
show up in make_prereqs_* on a rebuild.
We could move the filter into fixdep and filter based on the new .d
file, so the overlap is removed already on a clean build.
thanks,
Luis
--
Luis Augenstein * luis.augenstein@tngtech.com * +4915225275761
TNG Technology Consulting GmbH, Beta-Str. 13, 85774 Unterföhring
Geschäftsführer: Dr. Robert Dahlke, Thomas Endres, Moritz Prinz
Aufsichtsratsvorsitzender: Henrik Klagges
Sitz: Unterföhring * Registergericht: Amtsgericht München *
Handelsregisternummer: HRB 135082
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
next prev parent reply other threads:[~2026-08-21 20:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-14 11:21 [PATCH 0/1] kbuild: record real-prereqs in .cmd files Luis Augenstein
2026-08-14 11:21 ` [PATCH 1/1] " Luis Augenstein
2026-08-18 19:51 ` Nathan Chancellor
2026-08-21 19:57 ` Luis Augenstein [this message]
2026-08-25 3:22 ` Nathan Chancellor
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=1efb52b4-1a78-4c4e-aea1-6c8b426a8538@tngtech.com \
--to=luis.augenstein@tngtech.com \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=kstewart@linuxfoundation.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maximilian.huber@tngtech.com \
--cc=nathan@kernel.org \
--cc=nsc@kernel.org \
/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 NNTP newsgroup(s).