linux-kernel - Re: [PATCH 0/6] regulator: qcom_spmi: Add PM8909, PM8019 and PMA8084

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:   Wed, 27 Sep 2023 10:58:06 +0200
From:   Mark Brown <broonie@...nel.org>
To:     Stephan Gerhold <stephan@...hold.net>
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>,
        Robert Marko <robimarko@...il.com>,
        linux-arm-msm@...r.kernel.org, linux-kernel@...r.kernel.org,
        devicetree@...r.kernel.org,
        Stephan Gerhold <stephan.gerhold@...nkonzept.com>
Subject: Re: [PATCH 0/6] regulator: qcom_spmi: Add PM8909, PM8019 and
 PMA8084

On Tue, 12 Sep 2023 09:49:48 +0200, Stephan Gerhold wrote:
> Add the necessary definitions for the PM8909, PM8019 and PMA8084 PMIC to
> the qcom_spmi-regulator driver to allow reading the actual voltages
> applied to the hardware at runtime. This is mainly intended for
> debugging since the regulators are usually controlled through the
> RPM firmware (via qcom_smd-regulator).
> 
> These PMICs are used on totally different platforms (MSM8909, MDM9607,
> MSM8974/APQ8084). Each PMIC addition is independent and useful on it
> own. I only bundled them to simplify review.
> 
> [...]

Applied to

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

Thanks!

[1/6] dt-bindings: regulator: qcom,spmi: Document PM8909
      commit: 6f20872035378ab2311cc901f8f94f8718f1b17f
[2/6] regulator: qcom_spmi: Add PM8909 regulators
      commit: 813d01a40ae7c0c67681c82edce8463fbbd84b08
[3/6] dt-bindings: regulator: qcom,spmi: Document PM8019
      commit: 350aab7f8f2c7d7368d2bbc47717696a51014078
[4/6] regulator: qcom_spmi: Add PM8019 regulators
      commit: 5b30cb2a317a8e2636f724e8ebf5cbe3849e786e
[5/6] dt-bindings: regulator: qcom,spmi: Document PMA8084
      commit: f72d04235781cf89410ffd750109f4b9931c50ea
[6/6] regulator: qcom_spmi: Add PMA8084 regulators
      commit: 317aa3c4fe708fcbee5b9fe5fc25e1b9e92b83f5

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