linux-kernel - Re: [PATCH 0/3] Enable DVFS support for IPQ6018

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: <159614812412.1677.11866049151869161352.b4-ty@kernel.org>
Date:   Thu, 30 Jul 2020 23:28:44 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Kathiravan T <kathirav@...eaurora.org>,
        linux-kernel@...r.kernel.org, bjorn.andersson@...aro.org,
        robh+dt@...nel.org, agross@...nel.org,
        linux-arm-msm@...r.kernel.org, lgirdwood@...il.com,
        devicetree@...r.kernel.org, sivaprak@...eaurora.org
Subject: Re: [PATCH 0/3] Enable DVFS support for IPQ6018

On Thu, 30 Jul 2020 14:19:21 +0530, Kathiravan T wrote:
> Add A53 PLL, APCS clock, RPM Glink, RPM message RAM, cpu-opp-table,
> SMPA2 regulator to enable the cpu frequency on IPQ6018.
> 
> Kathiravan T (3):
>   dt-bindings: mailbox: add compatible for the IPQ6018 SoC
>   dt-bindings: regulator: add the sub node names for the MP5496 PMIC
>   arm64: dts: ipq6018: enable DVFS support
> 
> [...]

Applied to

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

Thanks!

[1/1] regulator: add the sub node names for the MP5496 PMIC
      commit: bcb3b2a7639db2412875520cddc3abd179068793

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