From: Nathan Chancellor <nathan@kernel.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: open list <linux-kernel@vger.kernel.org>,
lkft-triage@lists.linaro.org,
Linux Regressions <regressions@lists.linux.dev>,
clang-built-linux <llvm@lists.linux.dev>,
Nick Desaulniers <ndesaulniers@google.com>,
Dan Carpenter <dan.carpenter@linaro.org>,
Arnd Bergmann <arnd@arndb.de>,
Ben Copeland <benjamin.copeland@linaro.org>,
Anders Roxell <anders.roxell@linaro.org>
Subject: Re: next-20250819: sdhci-cadence.c error variable 'hrs37_mode' is uninitialized when used here [-Werror,-Wuninitialized]
Date: Wed, 20 Aug 2025 09:23:04 -0700 [thread overview]
Message-ID: <20250820162304.GD3805667@ax162> (raw)
In-Reply-To: <CA+G9fYtS9nDqC7g-B4285gmxDNRkYQixyPYMuzgDg5-sy2FumQ@mail.gmail.com>
Hi Naresh,
On Wed, Aug 20, 2025 at 06:43:51PM +0530, Naresh Kamboju wrote:
> The following build warnings / errors noticed with arm64 defconfig
> and x86 allyesconfig with clang-20 and clang-nightly toolchains.
>
> Regression Analysis:
> - New regression? yes
> - Reproducibility? yes
>
> Build regression: next-20250819 sdhci-cadence.c error variable
> 'hrs37_mode' is uninitialized when used here [-Werror,-Wuninitialized]
>
> Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
>
> ## Build log
> drivers/mmc/host/sdhci-cadence.c:297:9: error: variable 'hrs37_mode'
> is uninitialized when used here [-Werror,-Wuninitialized]
> 297 | writel(hrs37_mode, hrs37_reg);
> | ^~~~~~~~~~
> drivers/mmc/host/sdhci-cadence.c:291:16: note: initialize the variable
> 'hrs37_mode' to silence this warning
> 291 | u32 hrs37_mode;
> | ^
> | = 0
Thanks for the report. I sent a fix for this yesterday:
https://lore.kernel.org/20250819-mmc-sdhci-cadence-fix-uninit-hrs37_mode-v1-1-94aa2d0c438a@kernel.org/
Cheers,
Nathan
prev parent reply other threads:[~2025-08-20 16:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-20 13:13 next-20250819: sdhci-cadence.c error variable 'hrs37_mode' is uninitialized when used here [-Werror,-Wuninitialized] Naresh Kamboju
2025-08-20 16:23 ` Nathan Chancellor [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=20250820162304.GD3805667@ax162 \
--to=nathan@kernel.org \
--cc=anders.roxell@linaro.org \
--cc=arnd@arndb.de \
--cc=benjamin.copeland@linaro.org \
--cc=dan.carpenter@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=llvm@lists.linux.dev \
--cc=naresh.kamboju@linaro.org \
--cc=ndesaulniers@google.com \
--cc=regressions@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