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

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: <168361435697.303261.4023695080353832209.b4-ty@kernel.org>
Date:   Tue, 09 May 2023 15:39:16 +0900
From:   Mark Brown <broonie@...nel.org>
To:     Liam Girdwood <lgirdwood@...il.com>,
        Rob Herring <robh+dt@...nel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
        Mårten Lindahl <marten.lindahl@...s.com>
Cc:     linux-kernel@...r.kernel.org, devicetree@...r.kernel.org,
        kernel@...s.com
Subject: Re: [PATCH v3 0/2] regulator: Add support for TPS6287x

On Mon, 08 May 2023 15:14:06 +0200, Mårten Lindahl wrote:
> This series adds basic support for TI's TPS62870/TPS62871/TPS62872/
> TPS62873 high-frequency single-channel step-down converters with an
> I2C interface.
> 
> The devices can operate in power save mode for maximum efficiency, or
> forced-PWM mode for best transient performance and lowest output
> voltage ripple. All chip variants have four output voltage ranges and
> the driver changes active range depending on the requested voltage
> setting.
> 
> [...]

Applied to

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

Thanks!

[1/2] regulator: dt-bindings: Add bindings for TPS6287x
      commit: 034008dd227877cca1588d66e2df505f5fae26c9
[2/2] regulator: Add support for TI TPS6287x regulators
      commit: 7b0518fbf2befd7c4afb81eb06c95c8fc93998be

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