From: sashiko-bot@kernel.org
To: "Leo Yan" <leo.yan@arm.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: [PATCH v7 02/23] tools/thermal: Fix typo
Date: Tue, 02 Jun 2026 14:52:26 +0000 [thread overview]
Message-ID: <20260602145228.426A91F00893@smtp.kernel.org> (raw)
In-Reply-To: <20260602-tools_build_fix_zero_init-v7-2-631baf679fe7@arm.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] Fixing the `CFGLAS` typo to `CFLAGS` introduces linker flags (`-Wl,-lthermal` and `-Wl,-L.`) into the C compilation phase (`CFLAGS`). This breaks the build under Clang because the unused linker arguments during the `-c` compilation step trigger a warning that is turned into a fatal error by `-Werror`. Furthermore, these flags are useless because `CFLAGS` is not even passed to the `$(CC) --shared` link step in these Makefiles.
--
commit 93498abb92499dd9b72fc403e55f192942d97b46
Author: Leo Yan <leo.yan@arm.com>
tools/thermal: Fix typo
This commit fixes a typo in the tools/thermal/lib/Makefile, changing CFGLAS
to CFLAGS for the thermal library linker flags.
> diff --git a/tools/thermal/lib/Makefile b/tools/thermal/lib/Makefile
> --- a/tools/thermal/lib/Makefile
> +++ b/tools/thermal/lib/Makefile
> @@ -60,8 +60,8 @@ override CFLAGS += $(EXTRA_WARNINGS)
> override CFLAGS += -Werror -Wall
> override CFLAGS += -fPIC
> override CFLAGS += $(INCLUDES)
> -override CFGLAS += -Wl,-L.
> -override CFGLAS += -Wl,-lthermal
> +override CFLAGS += -Wl,-L.
> +override CFLAGS += -Wl,-lthermal
[Severity: Low]
Does adding these linker flags into the C compilation phase break the build
when compiling with Clang?
Since the Makefile also specifies -Werror, passing -Wl,-lthermal and -Wl,-L.
during the C compilation step might trigger a fatal unused argument warning
under Clang.
Are these linker flags actually needed in CFLAGS, or should they be added to
LDFLAGS instead, considering CFLAGS doesn't appear to be passed to the shared
link step?
Also, does the prior commit in this series introduce this same behavior in
tools/lib/thermal/Makefile by fixing an identical typo?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260602-tools_build_fix_zero_init-v7-0-631baf679fe7@arm.com?part=2
next prev parent reply other threads:[~2026-06-02 14:52 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-02 14:40 [PATCH v7 00/23] tools build: Append -fzero-init-padding-bits=all option Leo Yan
2026-06-02 14:40 ` [PATCH v7 01/23] tools: lib: thermal: Fix typo Leo Yan
2026-06-02 14:54 ` sashiko-bot
2026-06-02 14:40 ` [PATCH v7 02/23] tools/thermal: " Leo Yan
2026-06-02 14:52 ` sashiko-bot [this message]
2026-06-02 14:40 ` [PATCH v7 03/23] tools: lib: thermal: Initialize CFLAGS before including Makefile.include Leo Yan
2026-06-02 14:56 ` sashiko-bot
2026-06-02 14:40 ` [PATCH v7 04/23] tools/thermal: " Leo Yan
2026-06-02 14:40 ` [PATCH v7 05/23] selftests/nolibc: Use a dedicated cross cc-option helper Leo Yan
2026-06-02 15:02 ` sashiko-bot
2026-06-02 14:40 ` [PATCH v7 06/23] tools build: Append -fzero-init-padding-bits=all to extra cflags Leo Yan
2026-06-02 15:04 ` sashiko-bot
2026-06-02 14:40 ` [PATCH v7 07/23] perf build: Append extra host flags Leo Yan
2026-06-02 14:40 ` [PATCH v7 08/23] tools build: Append extra host CFLAGS for fixdep Leo Yan
2026-06-02 15:00 ` sashiko-bot
2026-06-02 14:40 ` [PATCH v7 09/23] tools: bootconfig: Append extra cflags Leo Yan
2026-06-02 14:40 ` [PATCH v7 10/23] tools: counter: " Leo Yan
2026-06-02 14:40 ` [PATCH v7 11/23] tools: dma: " Leo Yan
2026-06-02 14:40 ` [PATCH v7 12/23] tools: gpio: " Leo Yan
2026-06-02 14:40 ` [PATCH v7 13/23] tools: hv: " Leo Yan
2026-06-02 14:40 ` [PATCH v7 14/23] tools: iio: " Leo Yan
2026-06-02 14:40 ` [PATCH v7 15/23] tools: mm: " Leo Yan
2026-06-02 14:40 ` [PATCH v7 16/23] tools: objtool: Append extra host cflags Leo Yan
2026-06-02 14:40 ` [PATCH v7 17/23] tools: power: acpi: Append extra cflags Leo Yan
2026-06-02 15:07 ` sashiko-bot
2026-06-02 14:40 ` [PATCH v7 18/23] tools: power: x86/intel-speed-select: " Leo Yan
2026-06-02 14:40 ` [PATCH v7 19/23] tools: sched_ext: " Leo Yan
2026-06-02 14:40 ` [PATCH v7 20/23] tools: spi: " Leo Yan
2026-06-02 14:40 ` [PATCH v7 21/23] tools: tracing: " Leo Yan
2026-06-02 14:40 ` [PATCH v7 22/23] tools: usb: " Leo Yan
2026-06-02 14:40 ` [PATCH v7 23/23] selftests: Include tools Makefile.include Leo Yan
2026-06-02 15:15 ` sashiko-bot
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=20260602145228.426A91F00893@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=leo.yan@arm.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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