From: Luis Augenstein <luis.augenstein@tngtech.com>
To: "Bird, Tim" <Tim.Bird@sony.com>, "nathan@kernel.org" <nathan@kernel.org>
Cc: Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Greg KroahHartman <gregkh@linuxfoundation.org>,
Kate Stewart <kstewart@linuxfoundation.org>,
"maximilian.huber@tngtech.com" <maximilian.huber@tngtech.com>
Subject: Re: [PATCH v6 00/15] add SPDX SBOM generation script
Date: Fri, 15 May 2026 15:48:47 +0200 [thread overview]
Message-ID: <80eb0431-06f3-4d76-a2d9-b9df383ca323@tngtech.com> (raw)
In-Reply-To: <MW5PR13MB5632E740EE09E377C6E076E7FD062@MW5PR13MB5632.namprd13.prod.outlook.com>
[-- Attachment #1.1: Type: text/plain, Size: 2037 bytes --]
On 5/13/26 20:25, Bird, Tim wrote:
> Hey KernelSBom people,
>
> I got the following error message when using KernelSBom (both with the v5 release and the recent v6 release)
>
> I was doing a an arm64 defconfig build. I can work around the problem using your handy
> "--do-not-fail-on-unknown-build-command" option to the sbom generator, but thought I
> should report the issue.
>
> ==== error message ====
> ...
> GEN sbom-source.spdx.json sbom-build.spdx.json sbom-output.spdx.json
> [ERROR] File "/home/tbird/work/torvalds/linux/scripts/sbom/sbom/cmd_graph/savedcmd_parser/savedcmd_parser.py", line 33, in log_error_or_warning
> Skipped parsing command /bin/sh -e /home/tbird/work/torvalds/linux/arch/arm64/tools/gen-kernel-hwcaps.sh /home/tbird/work/torvalds/linux/arch/arm64/include/uapi/asm/hwcap.h > arch/arm64/include/generated/asm/kernel-hwcap.h because no matching parser was found
> =====================
>
> arch/arm64/tools/gen-kernel-hwcaps.sh is a simple scripts that does some simple
> transformations (using sed) on lines from the input file. As you can see, the build command takes
> arch/arm64/include/uapi/asm/hwcap.h and transforms it into $KBUILD_OUTPUT/arch/arm64/include/generated/asm/kernel-hwcap.h
>
> I think this should be easy to add to your command line parser. Just wanted to bring it to your attention.
>
Yes, thanks a lot for reporting the issue.
gen-kernel-hwcaps.sh is a new script that was added a month ago.
I will add a corresponding command parser with the next version.
> Great tool, by the way. I'm talking about it at OSSNA next week, and was just doing some testing on different
> platforms.
Cool! Happy to hear that :)
Best,
Luis
--
Luis Augenstein * luis.augenstein@tngtech.com * +4915225275761
TNG Technology Consulting GmbH, Beta-Str. 13, 85774 Unterföhring
Geschäftsführer: Henrik Klagges, Dr. Robert Dahlke, Thomas Endres
Aufsichtsratsvorsitzender: Moritz Prinz
Sitz: Unterföhring * Amtsgericht München * HRB 135082
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
next prev parent reply other threads:[~2026-05-15 13:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-13 18:25 [PATCH v6 00/15] add SPDX SBOM generation script Bird, Tim
2026-05-15 13:48 ` Luis Augenstein [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-05-07 17:38 Luis
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=80eb0431-06f3-4d76-a2d9-b9df383ca323@tngtech.com \
--to=luis.augenstein@tngtech.com \
--cc=Tim.Bird@sony.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 \
/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