linux-kernel - Re: [PATCH 1/2] regulator: qcom

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:   Mon, 05 Oct 2020 18:54:33 +0100
From:   Mark Brown <broonie@...nel.org>
To:     linux-kernel@...r.kernel.org,
        Kathiravan T <kathirav@...eaurora.org>,
        Liam Girdwood <lgirdwood@...il.com>,
        devicetree@...r.kernel.org, linux-arm-msm@...r.kernel.org,
        Vladimir Lypak <junak.pub@...il.com>,
        Bjorn Andersson <bjorn.andersson@...aro.org>,
        Rob Herring <robh+dt@...nel.org>,
        Andy Gross <agross@...nel.org>
Subject: Re: [PATCH 1/2] regulator: qcom_smd: add pm8953 regulators

On Sun, 4 Oct 2020 11:34:12 +0300, Vladimir Lypak wrote:
> The PM8953 is commonly used on board with MSM8953 SoCs or its variants:
> APQ8053, SDM(SDA)450 and SDM(SDA)632.
> It provides 7 SMPS and 23 LDO regulators.

Applied to

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

Thanks!

[1/2] regulator: qcom_smd: add pm8953 regulators
      commit: b1a2fb10b8ef07a32061c53426303f73533d867b
[2/2] dt-bindings: regulator: document pm8950 and pm8953 smd regulators
      commit: 357dd65a9aa8ee0c77c94dc4601075a33f33e528

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