linux-kernel - Re: [PATCH] regulators: dt-bindings: gpio-regulator: Fix "gpios-states" and "states" array bounds

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: <170897221675.89041.15993993935283518276.b4-ty@kernel.org>
Date: Mon, 26 Feb 2024 18:30:16 +0000
From: Mark Brown <broonie@...nel.org>
To: Liam Girdwood <lgirdwood@...il.com>, 
 Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>, 
 Conor Dooley <conor+dt@...nel.org>, Rob Herring <robh@...nel.org>
Cc: linux-kernel@...r.kernel.org, devicetree@...r.kernel.org
Subject: Re: [PATCH] regulators: dt-bindings: gpio-regulator: Fix
 "gpios-states" and "states" array bounds

On Fri, 23 Feb 2024 17:07:51 -0700, Rob Herring wrote:
> The minimum number of array entries for "gpios-states" was not not
> specified, so the the default is the same as the max (8).
> 
> The minimum is also missing from "states", and the maximum is also wrong
> as it should be 2^(# of GPIO lines). Since there can be 1 to 8 GPIOs,
> the "states" range should be 2 to 256.
> 
> [...]

Applied to

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

Thanks!

[1/1] regulators: dt-bindings: gpio-regulator: Fix "gpios-states" and "states" array bounds
      commit: efe9a6da2292e68d45cd9e0eb1c31b85841d0c2a

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