linux-kernel - Re: [PATCH v2 0/2] Add support for power budget

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: <173715436899.82438.12417432089372586277.b4-ty@kernel.org>
Date: Fri, 17 Jan 2025 22:52:48 +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>, 
 Kory Maincent <kory.maincent@...tlin.com>
Cc: Thomas Petazzoni <thomas.petazzoni@...tlin.com>, 
 linux-kernel@...r.kernel.org, devicetree@...r.kernel.org, 
 Oleksij Rempel <o.rempel@...gutronix.de>, kernel@...gutronix.de
Subject: Re: [PATCH v2 0/2] Add support for power budget

On Wed, 15 Jan 2025 15:41:56 +0100, Kory Maincent wrote:
> In preparation for future support of PSE budget evaluation strategy and
> power management, we need the power budget value of the power supply.
> 
> This addition allows the regulator to track the available power
> budget, which will be essential for prioritizing ports when
> making power allocation decisions.
> 
> [...]

Applied to

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

Thanks!

[1/2] regulator: Add support for power budget
      commit: 42d7c87b4e1251f36eceac987e74623e7cda8577
[2/2] regulator: dt-bindings: Add regulator-power-budget-milliwatt property
      commit: 367a8200a91025289f9664e468fbc2b67c95e70e

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