linux-kernel - Re: [PATCH v1 0/4] TPS65219 Regulator Driver Cleanup Series

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: <173453161253.102936.10383553575204986057.b4-ty@kernel.org>
Date: Wed, 18 Dec 2024 14:20:12 +0000
From: Mark Brown <broonie@...nel.org>
To: aaro.koskinen@....fi, andreas@...nade.info, khilman@...libre.com, 
 rogerq@...nel.org, tony@...mide.com, lgirdwood@...il.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 v1 0/4] TPS65219 Regulator Driver Cleanup Series

On Tue, 17 Dec 2024 14:45:22 -0600, Shree Ramamoorthy wrote:
> This series is in preparation to add 2 PMIC devices to the TPS65219 driver.
> 
> The changes involve using dev_err_probe() for instances that have a chance
> of returning -EPORBE_DEFER, remove redundant code, and follow other PMIC
> regulator driver naming conventions. The intention is to remove unnecessary
> noise from the new PMIC device patches added to this driver.
> 
> [...]

Applied to

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

Thanks!

[1/4] regulator: tps65219: Use dev_err_probe() instead of dev_err()
      commit: e7ce0437709552a5f5e577c29f3dfde620153913
[2/4] regulator: tps65219: Update driver name
      commit: 2ef8310c464cac41a024fc6fd2910e51f10a38e7
[3/4] regulator: tps65219: Remove MODULE_ALIAS
      commit: ca321ef98b80eb282a4dcdd5231f666c610b0575
[4/4] regulator: tps65219: Remove debugging helper function
      commit: 64a6b577490c1c71f1a3bbdb3844717815214621

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