From: Dan Carpenter <dan.carpenter@linaro.org>
To: "Benoît Monin" <benoit.monin@bootlin.com>
Cc: Nathan Chancellor <nathan@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Ulf Hansson <ulf.hansson@linaro.org>,
linux-mmc@vger.kernel.org, llvm@lists.linux.dev,
patches@lists.linux.dev
Subject: Re: [PATCH] mmc: sdhci-cadence: Fix -Wuninitialized in sdhci_cdns_tune_blkgap()
Date: Wed, 20 Aug 2025 13:43:09 +0300 [thread overview]
Message-ID: <aKWmvWTtQ_QZYgEm@stanley.mountain> (raw)
In-Reply-To: <2560300.XAFRqVoOGU@benoit.monin>
On Wed, Aug 20, 2025 at 10:07:35AM +0200, Benoît Monin wrote:
> > --- a/drivers/mmc/host/sdhci-cadence.c
> > +++ b/drivers/mmc/host/sdhci-cadence.c
> > @@ -288,13 +288,12 @@ static int sdhci_cdns_tune_blkgap(struct mmc_host *mmc)
> > void __iomem *hrs38_reg = priv->hrs_addr + SDHCI_CDNS_HRS38;
> > int ret;
> > u32 gap;
> > - u32 hrs37_mode;
> >
> > /* Currently only needed in HS200 mode */
> > if (host->timing != MMC_TIMING_MMC_HS200)
> > return 0;
> >
> > - writel(hrs37_mode, hrs37_reg);
> > + writel(SDHCI_CDNS_HRS37_MODE_MMC_HS200, hrs37_reg);
> >
> > for (gap = 0; gap <= SDHCI_CDNS_HRS38_BLKGAP_MAX; gap++) {
> > writel(gap, hrs38_reg);
> >
> Thanks for the catch!
>
> I don't get how gcc does not raise a warning here, only clang does. I
> did build with gcc-11 and gcc-15 and they don't complain about this
> uninitialized variable.
>
We disabled uninitialized variable checking on GCC. It was too crazy
and especially if we want to use -Werror.
Smatch also detects this bug.
regards,
dan carpenter
next prev parent reply other threads:[~2025-08-20 10:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-19 17:28 [PATCH] mmc: sdhci-cadence: Fix -Wuninitialized in sdhci_cdns_tune_blkgap() Nathan Chancellor
2025-08-20 8:07 ` Benoît Monin
2025-08-20 10:43 ` Dan Carpenter [this message]
2025-08-20 16:20 ` Nathan Chancellor
2025-08-20 16:43 ` Ulf Hansson
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=aKWmvWTtQ_QZYgEm@stanley.mountain \
--to=dan.carpenter@linaro.org \
--cc=adrian.hunter@intel.com \
--cc=benoit.monin@bootlin.com \
--cc=linux-mmc@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=nathan@kernel.org \
--cc=patches@lists.linux.dev \
--cc=ulf.hansson@linaro.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