linux-kernel - Re: [PATCH v2 0/2] DA9121 regulator 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] [thread-next>] [day] [month] [year] [list]

Message-Id: <160442731509.14990.12967764099458293588.b4-ty@kernel.org>
Date:   Tue, 03 Nov 2020 18:15:15 +0000
From:   Mark Brown <broonie@...nel.org>
To:     lgirdwood@...il.com, support.opensource@...semi.com,
        Vincent Whitchurch <vincent.whitchurch@...s.com>
Cc:     devicetree@...r.kernel.org, robh+dt@...nel.org, kernel@...s.com,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 0/2] DA9121 regulator support

On Tue, 3 Nov 2020 11:00:19 +0100, Vincent Whitchurch wrote:
> This series adds support for the DA9121, a "High-Performance, 10 A, Dual-Phase
> DC-DC Converter".  The datasheet is currently available here:
> 
>  https://www.dialog-semiconductor.com/sites/default/files/da9121_datasheet_2v3.pdf
> 
> v2:
> - Let the core get the constraints itself from a subnode in the device tree.
> 
> [...]

Applied to

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

Thanks!

[1/2] regulator: Add DA9121
      commit: 1119c59404141200125af31f775d3fbbba52c651
[2/2] regulator: Add support for DA9121 regulator
      commit: e6ff10f24c587c1af705b898761e5df615fb0e1a

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