linux-kernel - Re: [PATCH 0/3] regulator: da9121: update DA914x support

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: <164553775693.596513.14016754692281018447.b4-ty@kernel.org>
Date:   Tue, 22 Feb 2022 13:49:16 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Adam Ward <Adam.Ward.opensource@...semi.com>
Cc:     linux-kernel@...r.kernel.org, Liam Girdwood <lgirdwood@...il.com>,
        Support Opensource <support.opensource@...semi.com>
Subject: Re: [PATCH 0/3] regulator: da9121: update DA914x support

On Tue, 22 Feb 2022 00:27:41 +0000, Adam Ward wrote:
> This series applies corrections and updates to DA914x support in the DA9121 driver
> 
>   - correct errors in current range
>   - update maximum voltage to spec update
>   - remove unwanted settings
> 
> 
> [...]

Applied to

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

Thanks!

[1/3] regulator: da9121: Fix DA914x current values
      commit: f0fdfc04fd974cea23351b830fcac0822ea19a51
[2/3] regulator: da9121: Fix DA914x voltage value
      commit: c8c57fbc1c5067b913077e948c7d957af6834ba3
[3/3] regulator: da9121: Remove surplus DA9141 parameters
      commit: 9c7cf33c53ce833b58de9e5c192b4736dbd09cb1

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