From: "Sverdlin, Alexander" <alexander.sverdlin@siemens.com>
To: "linux@armlinux.org.uk" <linux@armlinux.org.uk>,
"alexander.stein@ew.tq-group.com"
<alexander.stein@ew.tq-group.com>,
"arnd@arndb.de" <arnd@arndb.de>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"bruce.ashfield@gmail.com" <bruce.ashfield@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] tools: use basename to identify file in gen-mach-types
Date: Thu, 24 Sep 2026 08:58:21 +0000 [thread overview]
Message-ID: <1fd21bb7bbb09e1566c090dad29710765c24bbd2.camel@siemens.com> (raw)
In-Reply-To: <20250826142518.2583999-1-alexander.stein@ew.tq-group.com>
Hi all,
On Tue, 2025-08-26 at 16:25 +0200, Alexander Stein wrote:
> From: Bruce Ashfield <bruce.ashfield@gmail.com>
>
> FILENAME is replaced by the full path to the executing script. If
> the script is executed via a fully specified path, that is captured
> in the output. Although it doesn't impact the output, it does trigger
> reproducibility warnings/errors.
>
> So we introduce a basename() function in the script and use it to
> make sure the output file contains only the name of the awk script.
> The motivation for this change is Yocto emitting a build warning
> WARNING: linux-tq-6.12.41+git-r0 do_package_qa: QA Issue: File /usr/src/debug/linux-tq/6.12.41+git/arch/arm/include/generated/asm/mach-types.h in package linux-tq-src contains reference to TMPDIR [buildpaths]
>
> Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
> Signed-off-by: Alexander Stein <alexander.stein@ew.tq-group.com>
we use it for quite some time for TI AM335x builds, so the issue is
real and long-standing. The fix also makes sense to me.
Reviewed-by: Alexander Sverdlin <alexander.sverdlin@siemens.com>
Tested-by: Alexander Sverdlin <alexander.sverdlin@siemens.com>
Arnd, would you consider the patch for the soc tree?
Or should I rather add the patch to Russell's patch system?
> ---
> arch/arm/tools/gen-mach-types | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/arch/arm/tools/gen-mach-types b/arch/arm/tools/gen-mach-types
> index cbe1c33bb8710..ab69d408f9e12 100644
> --- a/arch/arm/tools/gen-mach-types
> +++ b/arch/arm/tools/gen-mach-types
> @@ -21,10 +21,14 @@ NF == 3 {
> num[nr] = ""; nr++
> }
>
> + function basename(file) {
> + sub(".*/", "", file)
> + return file
> + }
>
> END {
> printf("/*\n");
> - printf(" * This was automagically generated from %s!\n", FILENAME);
> + printf(" * This was automagically generated from %s!\n", basename(FILENAME));
> printf(" * Do NOT edit\n");
> printf(" */\n\n");
> printf("#ifndef __ASM_ARM_MACH_TYPE_H\n");
--
Alexander Sverdlin
Siemens AG
www.siemens.com
prev parent reply other threads:[~2026-09-24 8:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-26 14:25 Alexander Stein
2025-11-07 14:42 ` Alexander Stein
2026-09-24 8:58 ` Sverdlin, Alexander [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=1fd21bb7bbb09e1566c090dad29710765c24bbd2.camel@siemens.com \
--to=alexander.sverdlin@siemens.com \
--cc=alexander.stein@ew.tq-group.com \
--cc=arnd@arndb.de \
--cc=bruce.ashfield@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
/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®