linux-kernel - Re: [PATCH v1 0/2] regulator: pca9450: add input supply links

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] [thread-next>] [day] [month] [year] [list]

Message-Id: <176165378617.53238.7226737509811324588.b4-ty@kernel.org>
Date: Tue, 28 Oct 2025 12:16:26 +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>, 
 Oleksij Rempel <o.rempel@...gutronix.de>
Cc: kernel@...gutronix.de, linux-kernel@...r.kernel.org, 
 devicetree@...r.kernel.org
Subject: Re: [PATCH v1 0/2] regulator: pca9450: add input supply links

On Mon, 27 Oct 2025 13:44:13 +0100, Oleksij Rempel wrote:
> This series adds input supply definitions for the NXP PCA9450 PMIC.
> 
> Some systems detect power events such as undervoltage before the PMIC.
> To allow correct propagation of such events, each regulator must define
> its upstream input supply. The first patch updates the devicetree
> binding to document new *-supply properties, and the second patch adds
> matching .supply_name entries in the driver.
> 
> [...]

Applied to

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

Thanks!

[1/2] dt-bindings: regulator: nxp,pca9450: document input supplies
      commit: 86df0030b71d7172317d957df17524a7fd6232d4
[2/2] regulator: pca9450: link regulator inputs to supply groups
      commit: 4c33cef58965eb655a0ac8e243aa323581ec025f

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