linux-kernel - Re: [PATCH v3 0/3] regulator: dt-bindings: qcom,rpmh: minor cleanups and extend supplies

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: <165169800298.1752583.17813272460576782096.b4-ty@kernel.org>
Date:   Wed, 04 May 2022 22:00:02 +0100
From:   Mark Brown <broonie@...nel.org>
To:     linux-kernel@...r.kernel.org, krzysztof.kozlowski@...aro.org,
        linux-arm-msm@...r.kernel.org, lgirdwood@...il.com,
        devicetree@...r.kernel.org, robh+dt@...nel.org, agross@...nel.org,
        bjorn.andersson@...aro.org, krzysztof.kozlowski+dt@...aro.org
Subject: Re: [PATCH v3 0/3] regulator: dt-bindings: qcom,rpmh: minor cleanups and extend supplies

On Tue, 26 Apr 2022 12:54:58 +0200, Krzysztof Kozlowski wrote:
> Extend the RPMH regulator bindings with minor fixes and adding narrow supply
> matching.
> 
> Changes since v2
> ================
> 1. Remove "defs" method, because schema nows allows unevaluatedProperties
>    without references to other schemas.
> 2. Include maintainer change patch, previously sent separately.
> 
> [...]

Applied to

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

Thanks!

[1/3] regulator: dt-bindings: qcom,rpmh: update maintainers
      commit: a6d889a8fdbb8cb4b0d01f30f93357f3ffd61f06
[2/3] regulator: dt-bindings: qcom,rpmh: document supplies per variant
      commit: ba5d99609a5e6a3d0d9ac2574250208457d839cc
[3/3] regulator: dt-bindings: qcom,rpmh: document vdd-l7-bob-supply on PMR735A
      commit: e84f3c41a583408c7c67ed7824a7ff14ff40d045

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