linux-kernel - Re: [PATCH 0/2] regulator: qcom,rpmh: Add support for PM8450

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: <163838355339.2179928.6181194813033095813.b4-ty@kernel.org>
Date:   Wed, 01 Dec 2021 18:32:33 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Rob Herring <robh+dt@...nel.org>, Vinod Koul <vkoul@...nel.org>
Cc:     Liam Girdwood <lgirdwood@...il.com>,
        David Collins <collinsd@...eaurora.org>,
        Bjorn Andersson <bjorn.andersson@...aro.org>,
        linux-kernel@...r.kernel.org, linux-arm-msm@...r.kernel.org,
        devicetree@...r.kernel.org, Andy Gross <agross@...nel.org>
Subject: Re: [PATCH 0/2] regulator: qcom,rpmh: Add support for PM8450

On Wed, 1 Dec 2021 12:55:13 +0530, Vinod Koul wrote:
> This add the binding and driver update to support the PM8450 which is found
> in SM8450 platform
> 
> Vinod Koul (2):
>   regulator: qcom,rpmh: Add compatible for PM8450
>   regulator: qcom-rpmh: Add support for PM8450 regulators
> 
> [...]

Applied to

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

Thanks!

[1/2] regulator: qcom,rpmh: Add compatible for PM8450
      commit: fa3b06f59a03a3a4639755478e0cf5b508a1b454
[2/2] regulator: qcom-rpmh: Add support for PM8450 regulators
      commit: d69e19723f88a3ba6d4e0e52f51dd4c59cc2ae93

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