linux-kernel - Re: [PATCH] regulator: core: let dt properties override driver init

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: <173930122805.78581.16583188319428497284.b4-ty@kernel.org>
Date: Tue, 11 Feb 2025 19:13:48 +0000
From: Mark Brown <broonie@...nel.org>
To: Liam Girdwood <lgirdwood@...il.com>, 
 Jerome Brunet <jbrunet@...libre.com>
Cc: linux-kernel@...r.kernel.org, Luca Weiss <luca@...aweiss.eu>
Subject: Re: [PATCH] regulator: core: let dt properties override driver
 init_data

On Tue, 11 Feb 2025 16:48:06 +0100, Jerome Brunet wrote:
> This reverts commit cd7a38c40b231350a3cd0fd774f4e6bb68c4b411.
> 
> When submitting the change above, it was thought that the origin of the
> init_data should be a clear choice, from the driver or from DT but not
> both.
> 
> It turns out some devices, such as qcom-msm8974-lge-nexus5-hammerhead,
> relied on the old behaviour to override the init_data provided by the
> driver, making it some kind of default if none is provided by the platform.
> 
> [...]

Applied to

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

Thanks!

[1/1] regulator: core: let dt properties override driver init_data
      commit: 35e21de48e693af1dcfdbf2dc3d73dcfa3c8f2d9

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