linux-kernel - Re: [PATCH] dt-bindings: regulator: qcom,usb-vbus-regulator: clean up example

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: <170300194921.59203.15876137715050350812.b4-ty@kernel.org>
Date: Tue, 19 Dec 2023 16:05:49 +0000
From: Mark Brown <broonie@...nel.org>
To: Johan Hovold <johan+linaro@...nel.org>
Cc: Andy Gross <agross@...nel.org>, Bjorn Andersson <andersson@...nel.org>, 
 Konrad Dybcio <konrad.dybcio@...aro.org>, 
 Liam Girdwood <lgirdwood@...il.com>, Rob Herring <robh+dt@...nel.org>, 
 Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>, 
 Conor Dooley <conor+dt@...nel.org>, Wesley Cheng <quic_wcheng@...cinc.com>, 
 linux-arm-msm@...r.kernel.org, linux-kernel@...r.kernel.org, 
 devicetree@...r.kernel.org
Subject: Re: [PATCH] dt-bindings: regulator: qcom,usb-vbus-regulator: clean
 up example

On Tue, 19 Dec 2023 08:57:49 +0100, Johan Hovold wrote:
> Devicetree node names should be generic; fix up the
> qcom,usb-vbus-regulator binding example accordingly.
> 
> While at it, drop an unnecessary label and add a newline separator
> before the child node to improve readability.
> 
> 
> [...]

Applied to

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

Thanks!

[1/1] dt-bindings: regulator: qcom,usb-vbus-regulator: clean up example
      commit: d939c02359a656a624d03c6f14ccadae4a1c66ac

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