linux-kernel - Re: (subset) [PATCH 0/5] regulator: pca9450: collect some improvement patches

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: <173383575122.36957.4079934608520923537.b4-ty@kernel.org>
Date: Tue, 10 Dec 2024 13:02:31 +0000
From: Mark Brown <broonie@...nel.org>
To: Liam Girdwood <lgirdwood@...il.com>, Rob Herring <robh@...nel.org>, 
 Krzysztof Kozlowski <krzk+dt@...nel.org>, 
 Conor Dooley <conor+dt@...nel.org>, Robin Gong <yibin.gong@....com>, 
 Shawn Guo <shawnguo@...nel.org>, Sascha Hauer <s.hauer@...gutronix.de>, 
 Pengutronix Kernel Team <kernel@...gutronix.de>, 
 Fabio Estevam <festevam@...il.com>, Frank Li <Frank.Li@....com>
Cc: linux-kernel@...r.kernel.org, devicetree@...r.kernel.org, 
 imx@...ts.linux.dev, joy.zou@....com, linux-arm-kernel@...ts.infradead.org
Subject: Re: (subset) [PATCH 0/5] regulator: pca9450: collect some
 improvement patches

On Thu, 05 Dec 2024 11:51:08 -0500, Frank Li wrote:
> Add pca9452 support
> Use dev_err_probe() to simple code
> add pca9452 support in imx93-14x14 dts
> 
> 

Applied to

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

Thanks!

[1/5] regulator: pca9450: add enable_value for all bucks
      commit: 229773f90b1f886e8fd542f98b495c66e43be5ba
[2/5] regulator: pca9450: Use dev_err_probe() to simplify code
      commit: 0f5c601098bd3c9cdfea3e01aacdd9d0c4010ea7
[3/5] regulator: dt-bindings: pca9450: Add pca9452 support
      commit: 17b531c162e5dbdce9a184ccd1c730ae3f31576b
[4/5] regulator: pca9450: Add PMIC pca9452 support
      commit: 017b76fb8e5b6066f6791e7ad2387deb2c9c9a14

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