dt-bindings: regulator: Fix type of regulator-coupled-max-spread property
Subsystems (2)
PATCH 1/1 dt-bindings: regulator: Fix type of regulator-coupled-max-spread property
From: Thierry Reding <[email protected]>
According to the description and the various uses of this property it is meant to be an array of unsigned 32-bit values, so fixup the type to match that.
--- Documentation/devicetree/bindings/regulator/regulator.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
Documentation/devicetree/bindings/regulator/regulator.yaml +1 -1
@@ -218,7 +218,7 @@ properties: description: Array of maximum spread between voltages of coupled regulators in microvolts, each value in the array relates to the corresponding couple specified by the regulator-coupled-with property. - $ref: "/schemas/types.yaml#/definitions/uint32" + $ref: "/schemas/types.yaml#/definitions/uint32-array" regulator-max-step-microvolt: description: Maximum difference between current and target voltages
Signature · 1 line
2.33.1
Quoted 11 lines · Thierry Reding
From: Thierry Reding <[email protected]>
According to the description and the various uses of this property it is meant to be an array of unsigned 32-bit values, so fixup the type to match that.
Signed-off-by Thierry Reding <[email protected]>--- Documentation/devicetree/bindings/regulator/regulator.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
Mark Brown
maintainerQuoted 8 lines · Thierry Reding
From: Thierry Reding <[email protected]>
According to the description and the various uses of this property it is meant to be an array of unsigned 32-bit values, so fixup the type to match that.
[...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next
Thanks!
[1/1] dt-bindings: regulator: Fix type of regulator-coupled-max-spread property
commit: 8d2de3a548ad05fe09bca58f09ff1ab2e69cf40a
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