linux-kernel - Re: [PATCH] regulator: rename regulator-uv-survival-time-ms according to DT binding

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: <173461829322.132192.5287833100554891123.b4-ty@kernel.org>
Date: Thu, 19 Dec 2024 14:24:53 +0000
From: Mark Brown <broonie@...nel.org>
To: Liam Girdwood <lgirdwood@...il.com>, 
 Ahmad Fatoum <a.fatoum@...gutronix.de>
Cc: linux-kernel@...r.kernel.org, Rob Herring <robh@...nel.org>, 
 Krzysztof Kozlowski <krzk+dt@...nel.org>, 
 Conor Dooley <conor+dt@...nel.org>, devicetree@...r.kernel.org, 
 kernel@...gutronix.de
Subject: Re: [PATCH] regulator: rename regulator-uv-survival-time-ms
 according to DT binding

On Wed, 18 Dec 2024 20:54:53 +0100, Ahmad Fatoum wrote:
> The regulator bindings don't document regulator-uv-survival-time-ms, but
> the more descriptive regulator-uv-less-critical-window-ms instead.
> 
> Looking back at v3[1] and v4[2] of the series adding the support,
> the property was indeed renamed between these patch series, but
> unfortunately the rename only made it into the DT bindings with the
> driver code still using the old name.
> 
> [...]

Applied to

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

Thanks!

[1/1] regulator: rename regulator-uv-survival-time-ms according to DT binding
      commit: 13221496065fa12fac4f8a8e725444679ffddb78

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