linux-kernel - Re: [PATCH V2 0/6] Add frequency / voltage scaling support for IPQ6018 SoC

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: <159364222730.10880.10457847599595105286.b4-ty@kernel.org>
Date:   Wed, 01 Jul 2020 23:23:52 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Kathiravan T <kathirav@...eaurora.org>, lgirdwood@...il.com,
        linux-kernel@...r.kernel.org, linux-arm-msm@...r.kernel.org,
        devicetree@...r.kernel.org, robh+dt@...nel.org,
        bjorn.andersson@...aro.org, agross@...nel.org
Cc:     sivaprak@...eaurora.org
Subject: Re: [PATCH V2 0/6] Add frequency / voltage scaling support for IPQ6018 SoC

On Tue, 23 Jun 2020 10:47:46 +0530, Kathiravan T wrote:
> IPQ6018 SoC uses the PMIC MP5496. SMPA2 and LDOA2 regulator of MP5496
> controls the APSS and SDCC voltage scaling respectively. Add support
> for the same.
> 
> changes since V1:
> 	- Moved YAML conversion to the last as per Mark's comments
> 
> [...]

Applied to

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

Thanks!

[1/2] regulator: add MP5496 regulator compatible
      commit: 93e39d096d7312e38cf502be4e516cff7acf34fa
[2/2] regulator: qcom_smd: Add MP5496 regulators
      commit: 47894c859479a9e3472657c7acf2c7ba35778059

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