[v3] regulator: dt-bindings: qcom,usb-vbus-regulator: change node name

From: Luca Weiss <luca@z3ntu.xyz>

usb-vbus-regulator is a better generic node name than dcdc to change the
example to match.

Acked-by: Rob Herring <robh@kernel.org>
Signed-off-by: Luca Weiss <luca@z3ntu.xyz>
---
Changes in v3:
- No change, resend since all other patches from series have been merged

 .../devicetree/bindings/regulator/qcom,usb-vbus-regulator.yaml  | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

On Thu, 29 Dec 2022 20:15:43 +0100, luca@z3ntu.xyz wrote:
> usb-vbus-regulator is a better generic node name than dcdc to change the
> example to match.
> 
> 

Applied to

   broonie/regulator.git for-next

Thanks!

[1/1] regulator: dt-bindings: qcom,usb-vbus-regulator: change node name
      commit: d13da2f4c81602fc22cdf2cb13b15283b260e0d5

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

On Donnerstag, 29. Dezember 2022 23:50:24 CET Mark Brown wrote:
> On Thu, 29 Dec 2022 20:15:43 +0100, luca@z3ntu.xyz wrote:
> > usb-vbus-regulator is a better generic node name than dcdc to change the
> > example to match.
> 
> Applied to
> 
>    broonie/regulator.git for-next
> 
> Thanks!
> 
> [1/1] regulator: dt-bindings: qcom,usb-vbus-regulator: change node name
>       commit: d13da2f4c81602fc22cdf2cb13b15283b260e0d5
> 

Thank you and sorry about the mess on the v2.

Regards
Luca

> 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