linux-kernel - Re: [PATCH V4 0/4] regulator: da9121: add 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: <163838355167.2179928.18428295245396475167.b4-ty@kernel.org>
Date:   Wed, 01 Dec 2021 18:32:31 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Rob Herring <robh+dt@...nel.org>,
        Adam Ward <Adam.Ward.opensource@...semi.com>
Cc:     devicetree@...r.kernel.org, Liam Girdwood <lgirdwood@...il.com>,
        Support Opensource <support.opensource@...semi.com>,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH V4 0/4] regulator: da9121: add DA914x support

On Mon, 29 Nov 2021 22:10:09 +0000, Adam Ward wrote:
> This series extends the DA9121 driver to add support for related products:
> 
>   DA9141, 40A, Quad-Phase
>   DA9142, 20A, Dual-Phase
> 
> The changing of current limit when active is now prohibited, for the range,
> due to possibility of undefined behaviour during transition
> 
> [...]

Applied to

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

Thanks!

[1/4] dt-bindings: da9121: Remove erroneous compatible from binding
      commit: b9c044b7d63b2ffae9664349721c80c4ab3e56c9
[2/4] dt-bindings: da9121: Add DA914x binding info
      commit: d07fef2fcd4d79198a700f4b4d2ca4670649c9ff
[3/4] regulator: da9121: Prevent current limit change when enabled
      commit: 24f0853228f3b98f1ef08d5824376c69bb8124d2
[4/4] regulator: da9121: Add DA914x support
      commit: c5187a245e9bb0af2da8d37ede191569c824c66b

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