linux-kernel - Re: [PATCH] regulator: pf8x00: Use regulator_map_voltage_ascend for pf8x00_buck7

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] [day] [month] [year] [list]

Message-Id: <161464183214.31485.8914564217194445331.b4-ty@kernel.org>
Date:   Mon, 01 Mar 2021 23:37:12 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Axel Lin <axel.lin@...ics.com>
Cc:     linux-kernel@...r.kernel.org,
        Adrien Grassein <adrien.grassein@...il.com>,
        Jagan Teki <jagan@...rulasolutions.com>,
        Liam Girdwood <lgirdwood@...il.com>
Subject: Re: [PATCH] regulator: pf8x00: Use regulator_map_voltage_ascend for pf8x00_buck7_ops

On Tue, 16 Feb 2021 14:01:28 +0800, Axel Lin wrote:
> The voltages in pf8x00_sw7_voltages are in ascendant order, so use
> regulator_map_voltage_ascend.

Applied to

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

Thanks!

[1/1] regulator: pf8x00: Use regulator_map_voltage_ascend for pf8x00_buck7_ops
      commit: 6930ab7ac03c1be5d1944473cbf327c9d4d14ce4

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