linux-kernel - Re: [PATCH] regulator: ltc3589: Convert to use regulator_set_ramp_delay

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]

Date:   Tue,  8 Jun 2021 17:06:31 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Axel Lin <axel.lin@...ics.com>
Cc:     Mark Brown <broonie@...nel.org>,
        Liam Girdwood <lgirdwood@...il.com>,
        linux-kernel@...r.kernel.org,
        Philipp Zabel <p.zabel@...gutronix.de>,
        Bernhard Walle <bernhard@...lle.de>
Subject: Re: [PATCH] regulator: ltc3589: Convert to use regulator_set_ramp_delay_regmap

On Fri, 4 Jun 2021 19:58:03 +0800, Axel Lin wrote:
> Use regulator_set_ramp_delay_regmap instead of open-coded
> 
> LTC3589_LINEAR_REG() no longer call LTC3589_REG() now.
> Only LTC3589_LINEAR_REG() needs to set go_bit, thus remove go_bit
> parameter from LTC3589_REG() macro.

Applied to

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

Thanks!

[1/1] regulator: ltc3589: Convert to use regulator_set_ramp_delay_regmap
      commit: ba6622c43381e7045f8bc5438089ae53054fdf83

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