From: "Arnd Bergmann" <arnd@arndb•de>
To: "Naresh Kamboju" <naresh.kamboju@linaro•org>,
"open list" <linux-kernel@vger•kernel.org>,
linux-next <linux-next@vger•kernel.org>,
lkft-triage@lists•linaro.org, llvm@lists•linux.dev
Cc: "Rafael J . Wysocki" <rafael@kernel•org>,
"Viresh Kumar" <viresh.kumar@linaro•org>,
"Linux PM" <linux-pm@vger•kernel.org>,
"Nathan Chancellor" <nathan@kernel•org>,
"Stuart Hayes" <stuart.w.hayes@gmail•com>
Subject: Re: x86: clang: acpi-cpufreq.c:970:24: error: variable 'ret' is uninitialized when used here [-Werror,-Wuninitialized]
Date: Thu, 10 Nov 2022 12:19:07 +0100 [thread overview]
Message-ID: <f22ea97e-9d76-4c8b-a0c9-698db6e69a9f@app.fastmail.com> (raw)
In-Reply-To: <CA+G9fYtaNmXOKnwH_ih9vZyFeaD+Lvzxf3WTbAV50rBtwkPxpQ@mail.gmail.com>
On Thu, Nov 10, 2022, at 12:14, Naresh Kamboju wrote:
> [Please ignore email this if it is already reported]
>
> Kernel build warning noticed on x86_64 with clang toolchain [1].
> Build failures noticed from next-20221108 .. next-20221110.
>
> Reported-by: Linux Kernel Functional Testing <lkft@linaro•org>
>
> make --silent --keep-going --jobs=8
> O=/home/tuxbuild/.cache/tuxmake/builds/1/build LLVM=1 LLVM_IAS=1
> ARCH=x86_64 SRCARCH=x86 CROSS_COMPILE=x86_64-linux-gnu- HOSTCC=clang
> CC=clang
> drivers/cpufreq/acpi-cpufreq.c:970:24: error: variable 'ret' is
> uninitialized when used here [-Werror,-Wuninitialized]
> acpi_cpufreq_online = ret;
> ^~~
> drivers/cpufreq/acpi-cpufreq.c:960:9: note: initialize the variable
> 'ret' to silence this warning
> int ret;
> ^
> = 0
> 1 error generated.
This is caused by 13fdbc8b8da6 ("cpufreq: ACPI: Defer setting boost MSRs"),
which removes the initialization of this variable.
Arnd
next prev parent reply other threads:[~2022-11-10 11:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-10 11:14 x86: clang: acpi-cpufreq.c:970:24: error: variable 'ret' is uninitialized when used here [-Werror,-Wuninitialized] Naresh Kamboju
2022-11-10 11:19 ` Arnd Bergmann [this message]
2022-11-10 20:17 ` stuart hayes
2022-11-10 12:46 ` Nathan Chancellor
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=f22ea97e-9d76-4c8b-a0c9-698db6e69a9f@app.fastmail.com \
--to=arnd@arndb$(echo .)de \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux-pm@vger$(echo .)kernel.org \
--cc=lkft-triage@lists$(echo .)linaro.org \
--cc=llvm@lists$(echo .)linux.dev \
--cc=naresh.kamboju@linaro$(echo .)org \
--cc=nathan@kernel$(echo .)org \
--cc=rafael@kernel$(echo .)org \
--cc=stuart.w.hayes@gmail$(echo .)com \
--cc=viresh.kumar@linaro$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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