linux-kernel - Re: [PATCH 0/2] regulator: Add support for TPS6286x

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: <164434680631.1135477.3942083403967758360.b4-ty@kernel.org>
Date:   Tue, 08 Feb 2022 19:00:06 +0000
From:   Mark Brown <broonie@...nel.org>
To:     lgirdwood@...il.com,
        Vincent Whitchurch <vincent.whitchurch@...s.com>
Cc:     linux-kernel@...r.kernel.org, kernel@...s.com,
        devicetree@...r.kernel.org, robh+dt@...nel.org
Subject: Re: [PATCH 0/2] regulator: Add support for TPS6286x

On Fri, 4 Feb 2022 16:52:39 +0100, Vincent Whitchurch wrote:
> TI's TPS62864/TPS6286/TPS62868/TPS62869 are high-frequency synchronous
> step-down converters controlled via I2C.  There are differences in the
> electrical characteristics and packaging between the variants, but the
> register interfaces are identical.
> 
> This series adds basic support for these chips.
> 
> [...]

Applied to

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

Thanks!

[1/2] regulator: Add bindings for TPS62864x
      commit: 2f04aa69ab5c5c40d2e3e51fd73ce2ecb651e9ba
[2/2] regulator: Add support for TPS6286x
      commit: e2a01b4e8806087743e5ee42f9dcedfc741d4112

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