linux-kernel - Re: [PATCH] regulator: tps6594-regulator: Fix the number of irqs for TPS65224 and TPS6594

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] [thread-next>] [day] [month] [year] [list]

Message-Id: <171752972825.277656.2076276752460770735.b4-ty@kernel.org>
Date: Tue, 04 Jun 2024 20:35:28 +0100
From: Mark Brown <broonie@...nel.org>
To: lgirdwood@...il.com, Thomas Richard <thomas.richard@...tlin.com>
Cc: m.nirmaladevi@...s.com, bhargav.r@...s.com, lee@...nel.org, 
 linux-kernel@...r.kernel.org, gregory.clement@...tlin.com, 
 thomas.petazzoni@...tlin.com, u-kumar1@...com
Subject: Re: [PATCH] regulator: tps6594-regulator: Fix the number of irqs
 for TPS65224 and TPS6594

On Mon, 03 Jun 2024 19:01:00 +0200, Thomas Richard wrote:
> The number of irqs is computed to allocate the right amount of memory for
> the irq data. An array of struct tps6594_regulator_irq_data is allocated
> one time for all the irqs. Each irq uses one cell of the array.
> 
> If the computed number of irqs is not correct, not allocated memory could
> be used.
> 
> [...]

Applied to

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

Thanks!

[1/1] regulator: tps6594-regulator: Fix the number of irqs for TPS65224 and TPS6594
      commit: 8141b6da1763b9db009e5dcf873869bb31bcef45

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