linux-kernel - Re: [PATCH V3 0/4] 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]

Date:   Wed, 22 Jul 2020 01:57:20 +0100
From:   Mark Brown <broonie@...nel.org>
To:     robh+dt@...nel.org, Kathiravan T <kathirav@...eaurora.org>,
        linux-arm-msm@...r.kernel.org, linux-kernel@...r.kernel.org,
        agross@...nel.org, devicetree@...r.kernel.org,
        bjorn.andersson@...aro.org, lgirdwood@...il.com
Cc:     sricharan@...eaurora.org, sivaprak@...eaurora.org
Subject: Re: [PATCH V3 0/4] Add frequency / voltage scaling support for IPQ6018 SoC

On Mon, 20 Jul 2020 11:42:19 +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 V2:
> 	- Rebased on top of linux-next 20200717 tag
> 	- Addressed Rob's comment to drop the 'syscon' node in qcom,smd-rpm.yaml
> 	- Picked up the Reviewed-by tag for qcom,smd-rpm-regulator.yaml
> 	- Regulator patches part of V2 was picked up by Mark and it's available in linux-next tree
> 
> [...]

Applied to

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

Thanks!

[1/1] regulator: convert QCOM SMD-RPM regulator document to YAML schema
      commit: 175a1d84154d4077da437b873319bd094b266ab8

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