linux-kernel - Re: [PATCH drivers-next] regulator: ad5398: Fix incorrect power down bit mask

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: <173885010497.175639.5929120087903015610.b4-ty@kernel.org>
Date: Thu, 06 Feb 2025 13:55:04 +0000
From: Mark Brown <broonie@...nel.org>
To: michael.hennerich@...log.com, 
 Dheeraj Reddy Jonnalagadda <dheeraj.linuxdev@...il.com>
Cc: lgirdwood@...il.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH drivers-next] regulator: ad5398: Fix incorrect power
 down bit mask

On Thu, 06 Feb 2025 16:01:53 +0530, Dheeraj Reddy Jonnalagadda wrote:
> AD5398_SW_POWER_DOWN was defined with a bit position outside the valid
> range of the device's 16-bit register. The bitwise operation with an
> unsigned short would always evaluate to 0, making the power down check
> ineffective.
> 
> Update AD5398_SW_POWER_DOWN to use a valid bit position within the
> 16-bit range of the register.
> 
> [...]

Applied to

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

Thanks!

[1/1] regulator: ad5398: Fix incorrect power down bit mask
      commit: 0a7c85b516830c0bb088b0bdb2f2c50c76fc531a

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