linux-kernel - Re: (subset) [PATCH 0/3] Add PMG1110(Seco Jr) PMIC support

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] [thread-next>] [day] [month] [year] [list]

Message-Id: <163820434992.1716869.8358627296301312921.b4-ty@kernel.org>
Date:   Mon, 29 Nov 2021 16:45:49 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Bjorn Andersson <bjorn.andersson@...aro.org>,
        Rob Herring <robh+dt@...nel.org>,
        Satya Priya <quic_c_skakit@...cinc.com>
Cc:     linux-arm-msm@...r.kernel.org, linux-kernel@...r.kernel.org,
        devicetree@...r.kernel.org, mka@...omium.org,
        Liam Girdwood <lgirdwood@...il.com>,
        David Collins <collinsd@...eaurora.org>, swboyd@...omium.org
Subject: Re: (subset) [PATCH 0/3] Add PMG1110(Seco Jr) PMIC support

On Tue, 23 Nov 2021 17:19:24 +0530, Satya Priya wrote:
> This series depends on below series which adds the base CRD dts
> https://patchwork.kernel.org/project/linux-arm-msm/list/?series=584349
> 
> Satya Priya (3):
>   dt-bindings: regulator: Add compatible for pmg1110
>   regulator: qcom-rpmh: Add PMG1110 regulators
>   arm64: dts: qcom: sc7280: Add pmg1110 regulators for sc7280-crd
> 
> [...]

Applied to

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

Thanks!

[1/3] dt-bindings: regulator: Add compatible for pmg1110
      commit: ac88e9526d68f2532be3b4b439d45c0c8de7e170
[2/3] regulator: qcom-rpmh: Add PMG1110 regulators
      commit: 59eadd2af3f717f2ff70dbb6c153757dc1650651

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