From: Greg KH <gregkh@linuxfoundation.org>
To: Luis Augenstein <luis.augenstein@tngtech.com>
Cc: nathan@kernel.org, nsc@kernel.org, linux-kbuild@vger.kernel.org,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
maximilian.huber@tngtech.com
Subject: Re: [PATCH 00/14] Add SPDX SBOM generation tool
Date: Tue, 20 Jan 2026 07:08:44 +0100 [thread overview]
Message-ID: <2026012009-applied-napped-42e2@gregkh> (raw)
In-Reply-To: <eec88937-2afd-45cc-bf7c-28b383e27d5b@tngtech.com>
On Mon, Jan 19, 2026 at 09:08:14PM +0100, Luis Augenstein wrote:
> > Also, I don't know if this is even possible, or you care about it, but
> > if you have ANY sbom file present, it is not regenerated:
> > [...]
> > So, if I change the build config, which will change the sbom output,
> > will the sbom be regenerated?
> > Should it depend on the config .h files to know this?
>
> Thanks for pointing this out.
> Yes, we can add the following to the Makefile dependencies to ensure the
> SBOM is regenerated when the build changes:
> - $(objtree)/$(KBUILD_IMAGE)
> - $(objtree)/include/generated/autoconf.h
> - $(objtree)/modules.order (if CONFIG_MODULES is set)
>
> This should cover most changes.
> When you mentioned "config .h files," did you have any other specific
> files in mind that should be included as dependencies?
I was referring to the autoconf.h file, thanks for figuring that out, I
couldn't remember what the exact name was. So that should be sufficient
here.
thanks,
greg k-h
prev parent reply other threads:[~2026-01-20 6:08 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-19 6:47 [PATCH 00/14] Add SPDX SBOM generation tool Luis Augenstein
2026-01-19 6:47 ` [PATCH 01/14] tools/sbom: integrate tool in make process Luis Augenstein
2026-01-19 6:47 ` [PATCH 02/14] tools/sbom: setup sbom logging Luis Augenstein
2026-01-19 6:47 ` [PATCH 03/14] tools/sbom: add command parsers Luis Augenstein
2026-01-19 6:47 ` [PATCH 04/14] tools/sbom: add cmd graph generation Luis Augenstein
2026-01-19 6:47 ` [PATCH 05/14] tools/sbom: add additional dependency sources for cmd graph Luis Augenstein
2026-01-19 6:47 ` [PATCH 06/14] tools/sbom: add SPDX classes Luis Augenstein
2026-01-19 6:47 ` [PATCH 07/14] tools/sbom: add JSON-LD serialization Luis Augenstein
2026-01-19 6:47 ` [PATCH 08/14] tools/sbom: add shared SPDX elements Luis Augenstein
2026-01-19 6:47 ` [PATCH 09/14] tools/sbom: collect file metadata Luis Augenstein
2026-01-19 6:47 ` [PATCH 10/14] tools/sbom: add SPDX output graph Luis Augenstein
2026-01-19 6:47 ` [PATCH 11/14] tools/sbom: add SPDX source graph Luis Augenstein
2026-01-19 6:47 ` [PATCH 12/14] tools/sbom: add SPDX build graph Luis Augenstein
2026-01-19 6:47 ` [PATCH 13/14] tools/sbom: add unit tests for command parsers Luis Augenstein
2026-01-19 6:47 ` [PATCH 14/14] tools/sbom: Add unit tests for SPDX-License-Identifier parsing Luis Augenstein
2026-01-19 9:51 ` [PATCH 00/14] Add SPDX SBOM generation tool Greg KH
2026-01-19 10:00 ` Greg KH
2026-01-19 20:08 ` Luis Augenstein
2026-01-20 6:08 ` Greg KH [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=2026012009-applied-napped-42e2@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luis.augenstein@tngtech.com \
--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