regulator: rtq2208: Fix incorrect code section

From: ChiYuan Huang <[email protected]>

Remove the whitespace that checkpatch scaned.

---
 .../devicetree/bindings/regulator/richtek,rtq2208.yaml          | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

index a584ce54012c..022c1f197364 100644
@@ -39,7 +39,7 @@ properties:
 
   interrupts:
     maxItems: 1
-    
+
   richtek,mtp-sel-high:
     type: boolean
     description:

2.34.1

From: ChiYuan Huang <[email protected]>

Since the check for fixed LDO VOUT can be identified by the HW register, mark the unnecessary property as deprecated.

---
V3
- Separate trailing white removal into another commit

v2
- Mark the property as deprecated

---
 Documentation/devicetree/bindings/regulator/richtek,rtq2208.yaml | 1 +
 1 file changed, 1 insertion(+)

index 87accc6f13b8..a584ce54012c 100644
@@ -77,6 +77,7 @@ properties:
 
         properties:
           richtek,fixed-microvolt:
+            deprecated: true
             description: |
               This property can be used to set a fixed operating voltage that lies outside
               the range of the regulator's adjustable mode.

2.34.1

From: ChiYuan Huang <[email protected]>

The old v1 series are here for the reference
https://lore.kernel.org/lkml/[email protected]/

Since the subset of v1 patch series are accepted, there's only one document change are left and still need to be reviewed.

ChiYuan Huang (2):
regulator: dt-bindings: rtq2208: Mark fixed LDO VOUT property as
deprecated
regulator: dt-bindings: rtq2208: Cleanup whitespace

 .../devicetree/bindings/regulator/richtek,rtq2208.yaml         | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

2.34.1

Applied to

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

Thanks!

[1/2] regulator: dt-bindings: rtq2208: Mark fixed LDO VOUT property as deprecated

      commit: 64b3fb38b45f7f36954801c45d9b7c19d82d6f83
[2/2] regulator: dt-bindings: rtq2208: Cleanup whitespace
      commit: 5e9491370a58bee1784999aa42f48f1f7289f641

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