linux-kernel - Re: [PATCH][next] regulator: bd9576: Fix uninitializes variable may_have

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <162446430310.55481.3940596483000012413.b4-ty@kernel.org>
Date:   Wed, 23 Jun 2021 17:08:54 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Liam Girdwood <lgirdwood@...il.com>,
        Matti Vaittinen <matti.vaittinen@...rohmeurope.com>,
        linux-power@...rohmeurope.com,
        Colin King <colin.king@...onical.com>
Cc:     Mark Brown <broonie@...nel.org>, linux-kernel@...r.kernel.org,
        kernel-janitors@...r.kernel.org
Subject: Re: [PATCH][next] regulator: bd9576: Fix uninitializes variable may_have_irqs

On Tue, 22 Jun 2021 15:47:30 +0100, Colin King wrote:
> The boolean variable may_have_irqs is not ininitialized and is
> only being set to true in the case where chip is ROHM_CHIP_TYPE_BD9576.
> Fix this by ininitialized may_have_irqs to false.

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next

Thanks!

[1/1] regulator: bd9576: Fix uninitializes variable may_have_irqs
      commit: ddf275b219ab22bc07c14ac88c290694089dced0

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark