linux-kernel - Re: [PATCH 1/2] regulator: qcom_smd: add get

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Wed, 08 Jun 2022 11:49:16 +0100
From:   Mark Brown <broonie@...nel.org>
To:     linux-kernel@...r.kernel.org, agross@...nel.org,
        linux-arm-msm@...r.kernel.org, lgirdwood@...il.com,
        robimarko@...il.com, bjorn.andersson@...aro.org
Subject: Re: [PATCH 1/2] regulator: qcom_smd: add get_voltage to MP5496

On Sat, 4 Jun 2022 21:32:59 +0200, Robert Marko wrote:
> Add the get_voltage OP to MP5496 ops using the generic rpm_reg_get_voltage.
> 
> 

Applied to

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

Thanks!

[1/2] regulator: qcom_smd: add get_voltage to MP5496
      commit: f210f387c8c05ae0bd5312b8b6b85398c20b94f9
[2/2] regulator: qcom_smd: correct MP5496 ranges
      commit: 122e951eb8045338089b086c8bd9b0b9afb04a92

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