linux-kernel - Re: [PATCH] regulator (max5970): Fix IRQ handler

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: <170664353402.52247.17282452218035818991.b4-ty@kernel.org>
Date: Tue, 30 Jan 2024 19:38:54 +0000
From: Mark Brown <broonie@...nel.org>
To: Liam Girdwood <lgirdwood@...il.com>, 
 Naresh Solanki <naresh.solanki@...ements.com>
Cc: mazziesaccount@...il.com, 
 Patrick Rudolph <patrick.rudolph@...ements.com>, 
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH] regulator (max5970): Fix IRQ handler

On Tue, 30 Jan 2024 20:32:56 +0530, Naresh Solanki wrote:
> The max5970 datasheet gives the impression that IRQ status bits must
> be cleared by writing a one to set bits, as those are marked with 'R/C',
> however tests showed that a zero must be written.
> 
> Fixes an IRQ storm as the interrupt handler actually clears the IRQ
> status bits.
> 
> [...]

Applied to

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

Thanks!

[1/1] regulator (max5970): Fix IRQ handler
      commit: a3fa9838e8140584a6f338e8516f2b05d3bea812

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