linux-kernel - Re: [PATCH v3] regulator: dt-bindings: qcom,usb-vbus-regulator: change node name

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <4449469.LvFx2qVVIh@g550jk>
Date:   Fri, 30 Dec 2022 18:56:24 +0100
From:   Luca Weiss <luca@...tu.xyz>
To:     linux-arm-msm@...r.kernel.org, Mark Brown <broonie@...nel.org>
Cc:     ~postmarketos/upstreaming@...ts.sr.ht, phone-devel@...r.kernel.org,
        Rob Herring <robh@...nel.org>, 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>,
        Wesley Cheng <quic_wcheng@...cinc.com>,
        linux-kernel@...r.kernel.org, devicetree@...r.kernel.org
Subject: Re: [PATCH v3] regulator: dt-bindings: qcom,usb-vbus-regulator: change node
 name

On Donnerstag, 29. Dezember 2022 23:50:24 CET Mark Brown wrote:
> On Thu, 29 Dec 2022 20:15:43 +0100, luca@...tu.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