linux-kernel - Re: [PATCH 0/2] Add PM2250 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]

Message-Id: <163313363140.52167.8614698450886602712.b4-ty@kernel.org>
Date:   Sat,  2 Oct 2021 01:16:26 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Shawn Guo <shawn.guo@...aro.org>
Cc:     Mark Brown <broonie@...nel.org>, Rob Herring <robh+dt@...nel.org>,
        Kathiravan T <kathirav@...eaurora.org>,
        Bjorn Andersson <bjorn.andersson@...aro.org>,
        linux-arm-msm@...r.kernel.org, devicetree@...r.kernel.org,
        linux-kernel@...r.kernel.org,
        Loic Poulain <loic.poulain@...aro.org>
Subject: Re: [PATCH 0/2] Add PM2250 qcom_smd regulators

On Sun, 26 Sep 2021 16:45:47 +0800, Shawn Guo wrote:
> The series adds Qualcomm PM2250 smd-rpm regulators support.
> 
> Shawn Guo (2):
>   dt-bindings: regulator: Document PM2250 smd-rpm regulators
>   regulator: qcom_smd: Add PM2250 regulators
> 
> .../regulator/qcom,smd-rpm-regulator.yaml     |  4 ++
>  drivers/regulator/qcom_smd-regulator.c        | 49 +++++++++++++++++++
>  2 files changed, 53 insertions(+)
> 
> [...]

Applied to

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

Thanks!

[1/2] dt-bindings: regulator: Document PM2250 smd-rpm regulators
      commit: 482f8032f496d8fa1441da742fd57fadbb17fb3d
[2/2] regulator: qcom_smd: Add PM2250 regulators
      commit: 400c93151f4160cf75e065d40e3774a18c8555a0

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