linux-kernel - Re: [PATCH 0/3] regulator: qcom_smd: Add PM8909 and fix pm8916

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]

Date:   Thu, 30 Jun 2022 14:32:10 +0100
From:   Mark Brown <broonie@...nel.org>
To:     stephan.gerhold@...nkonzept.com
Cc:     bjorn.andersson@...aro.org, krzysztof.kozlowski+dt@...aro.org,
        linux-arm-msm@...r.kernel.org, lgirdwood@...il.com,
        agross@...nel.org, linux-kernel@...r.kernel.org,
        robh+dt@...nel.org, devicetree@...r.kernel.org
Subject: Re: [PATCH 0/3] regulator: qcom_smd: Add PM8909 and fix pm8916_pldo range

On Thu, 23 Jun 2022 11:46:11 +0200, Stephan Gerhold wrote:
> Fix the voltage range for the pm8916_pldo in the qcom_smd-regulator
> driver and add definitions for the regulators available in PM8909.
> 
> Stephan Gerhold (3):
>   regulator: qcom_smd: Fix pm8916_pldo range
>   regulator: dt-bindings: qcom,smd-rpm: Add PM8909
>   regulator: qcom_smd: Add PM8909 RPM regulators
> 
> [...]

Applied to

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

Thanks!

[1/3] regulator: qcom_smd: Fix pm8916_pldo range
      commit: e8977917e116d1571dacb8e9864474551c1c12bd
[2/3] regulator: dt-bindings: qcom,smd-rpm: Add PM8909
      commit: 8cbb948a7cc2875d09234e2ce0424bc501c370b9
[3/3] regulator: qcom_smd: Add PM8909 RPM regulators
      commit: bc4d193238be4ef8ecee1ba0e0371169ad448c31

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