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]
Date:   Tue, 23 Aug 2022 19:54:48 +0100
From:   Mark Brown <broonie@...nel.org>
To:     kristo@...nel.org, Jerome Neanne <jneanne@...libre.com>,
        dmitry.torokhov@...il.com, lgirdwood@...il.com, robh+dt@...nel.org,
        nm@...com
Cc:     narmstrong@...libre.com, lee.jones@...aro.org, msp@...libre.com,
        linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
        khilman@...libre.com, j-keerthy@...com, devicetree@...r.kernel.org,
        linux-input@...r.kernel.org
Subject: Re: (subset) [PATCH v3 00/10] Add support for TI TPS65219 PMIC.

On Fri, 5 Aug 2022 14:18:42 +0200, Jerome Neanne wrote:
> This driver supports
> - 3 Buck regulators and 4 LDOs
> - low-power standby mode
> - warm/soft reset
> - basic fault handling (via interrupts).
> - power button
> 
> [...]

Applied to

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

Thanks!

[04/10] regulator: dt-bindings: Add TI TPS65219 PMIC bindings
        commit: 4d2aed6ee306ccdcae51f550309bfb82ebf31b01
[08/10] regulator: drivers: Add TI TPS65219 PMIC regulators support
        commit: c12ac5fc3e0af29851785e557e243663b4fc7f4b

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

Powered by blists - more mailing lists