linux-kernel - Re: [PATCH v7 0/4] Add TI TPS65214 & TPS65215 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] [day] [month] [year] [list]

Message-Id: <174631700028.4095183.1037286484966079333.b4-ty@kernel.org>
Date: Sun, 04 May 2025 09:03:20 +0900
From: Mark Brown <broonie@...nel.org>
To: lgirdwood@...il.com, aaro.koskinen@....fi, andreas@...nade.info, 
 khilman@...libre.com, rogerq@...nel.org, tony@...mide.com, 
 linux-omap@...r.kernel.org, linux-kernel@...r.kernel.org, 
 Shree Ramamoorthy <s-ramamoorthy@...com>
Cc: m-leonard@...com, praneeth@...com
Subject: Re: [PATCH v7 0/4] Add TI TPS65214 & TPS65215 Regulator Support

On Fri, 25 Apr 2025 15:57:32 -0500, Shree Ramamoorthy wrote:
> Rebase patch series for 6.16 cycle. The related MFD series was integrated
> in mainline during 6.15 cycle [0].
> 
> TPS65214 and TPS65215 are Power Management Integrated Circuits (PMICs) that
> have significant register map overlap with TPS65219 and each other. The
> series introduces the 2 new PMICs and restructures the existing driver to
> support multiple devices.
> 
> [...]

Applied to

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

Thanks!

[1/4] regulator: tps65219: Update struct names
      commit: 8c04144e156b49980a786e80c855e41f6c71685c
[2/4] regulator: tps65219: Add support for TPS65215 regulator resources
      commit: 3f2e457efdad5af4164f155bd7ac902258a9b1ce
[3/4] regulator: tps65219: Add support for TPS65215 Regulator IRQs
      commit: 38c9f98db20a649a1f8454f507608b6aef0c9297
[4/4] regulator: tps65219: Add TI TPS65214 Regulator Support
      commit: f1471bc435afa31c8c0c58551922830dc8f4b06b

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