From: Luis Augenstein <luis.augenstein@tngtech.com>
To: Nicolas Schier <nsc@kernel.org>
Cc: nathan@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 v2 1/1] kbuild: record real-prereqs in .cmd files
Date: Mon, 12 Oct 2026 23:33:13 +0200 [thread overview]
Message-ID: <0e867541-15f9-49e6-8753-3a9e2f2f0e55@tngtech.com> (raw)
In-Reply-To: <179138436214.145576.15291381959921627967.b4-review@b4>
[-- Attachment #1.1: Type: text/plain, Size: 1791 bytes --]
On 10/7/26 16:46, Nicolas Schier wrote:
>> Record $(real-prereqs), the non-phony prerequisites of the target, in a
>> new metadata field:
>>
>> make_prereqs_<target> := <prerequisites>
>>
>> Write the field from both cmd_and_savecmd and cmd_and_fixdep.
>>
>> Update scripts/make_fit.py to read only savedcmd_* instead of parsing the
>> complete .cmd file.
>
> This sounds like a good thing; but I can't find that in the diff.
It's the first section in the diff in scripts/Kbuild.include.
The original sentence might have been a bit unclear though.
$(cmd-prereqs) is the new variable that is actually used by
cmd_and_savecmd and cmd_and_fixdep. However, since $(cmd-prereqs) is
just $(real-prereqs) with $(deps_) filtered out, I omitted this
intermediate step in the description. I will rephrase it in v3 to make
it more clear.
> Why do you defer the actual implementation in the SBOM scripts? From my
> point of view, the introduction of 'make_prereqs_<target>' looks good
> and I don't see a reason for waiting with the corresponding SBOM
> implementation.
I thought it would be a sensible boundary to first change Kbuild and
then separately update the SBOM tool to use the new information the
.cmd files offer. Also, when I posted this series, I simply didn't
have the SBOM patches finished yet. By now they are ready for review
as well, so I will include them in v3 of this series.
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 --]
prev parent reply other threads:[~2026-10-12 21:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-28 8:54 [PATCH v2 0/1] " Luis Augenstein
2026-08-28 8:54 ` [PATCH v2 1/1] " Luis Augenstein
2026-10-07 14:46 ` Nicolas Schier
2026-10-12 21:33 ` Luis Augenstein [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=0e867541-15f9-49e6-8753-3a9e2f2f0e55@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
all inboxes | Powered by JetHome®