linux-kernel - Re: (subset) [PATCH 0/6] Add Power Domains and Regulators in SDX65

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]

Date:   Fri, 18 Mar 2022 20:57:58 +0000
From:   Mark Brown <broonie@...nel.org>
To:     collinsd@...eaurora.org, lgirdwood@...il.com,
        linus.walleij@...aro.org, agross@...nel.org, robh+dt@...nel.org,
        rnayak@...eaurora.org, bjorn.andersson@...aro.org,
        Rohit Agarwal <quic_rohiagar@...cinc.com>
Cc:     devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
        linux-gpio@...r.kernel.org, linux-arm-msm@...r.kernel.org
Subject: Re: (subset) [PATCH 0/6] Add Power Domains and Regulators in SDX65

On Wed, 16 Mar 2022 11:37:11 +0530, Rohit Agarwal wrote:
> This series adds driver and dt-bindings related changes
> in SDX65 to add power domains and regulators.
> 
> Thanks,
> Rohit.
> 
> Rohit Agarwal (6):
>   regulator: dt-bindings: Add PMX65 compatibles
>   regulator: qcom-rpmh: Add support for SDX65
>   dt-bindings: power: Add rpm power domain bindings for SDX65
>   soc: qcom: rpmhpd: Add SDX65 power domains
>   dt-bindings: pinctrl: qcom-pmic-gpio: Add pmx65 support
>   pinctrl: qcom-pmic-gpio: Add support for pmx65
> 
> [...]

Applied to

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

Thanks!

[1/6] regulator: dt-bindings: Add PMX65 compatibles
      commit: e34855b99696433a26d86179552553c6c6fa69b8
[2/6] regulator: qcom-rpmh: Add support for SDX65
      commit: 5999f85ddeb436b4007878f251a30ccc8b9c638b

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