From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox@lists.infradead.org, Jules Maselbas <jmaselbas@zdiv.net>
Subject: Re: [PATCH] regulator: fan53555: suppress warning about uninitialized variable
Date: Mon, 17 Mar 2025 09:43:14 +0100 [thread overview]
Message-ID: <174220099476.4061406.12703222009405718514.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20250314152437.25675-1-jmaselbas@zdiv.net>
On Fri, 14 Mar 2025 16:24:37 +0100, Jules Maselbas wrote:
> In function 'fan53555_device_setup', a call to 'regmap_update_bits' is
> made with the mode_mask variable potentially uninitialized.
>
> This can be the case if di->vendor is FAN53526_VENDOR_FAIRCHILD and
> di->sleep_vsel_id is not handled by the case (neither FAN53555_VSEL_ID_0 nor FAN53555_VSEL_ID_1).
> I am not sure how likely it is to happen.
>
> [...]
Applied, thanks!
[1/1] regulator: fan53555: suppress warning about uninitialized variable
https://git.pengutronix.de/cgit/barebox/commit/?id=55d10d7aa06f (link may not be stable)
Best regards,
--
Sascha Hauer <s.hauer@pengutronix.de>
prev parent reply other threads:[~2025-03-17 8:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-14 15:24 Jules Maselbas
2025-03-17 8:43 ` Sascha Hauer [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=174220099476.4061406.12703222009405718514.b4-ty@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=jmaselbas@zdiv.net \
/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