linux-kernel - Re: [PATCH 0/2] regulator: Constify read-only regmap

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: <172012321044.121848.14079522267513199767.b4-ty@kernel.org>
Date: Thu, 04 Jul 2024 21:00:10 +0100
From: Mark Brown <broonie@...nel.org>
To: Support Opensource <support.opensource@...semi.com>, 
 Liam Girdwood <lgirdwood@...il.com>, 
 Javier Carrasco <javier.carrasco.cruz@...il.com>
Cc: linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/2] regulator: Constify read-only regmap_config struct

On Thu, 04 Jul 2024 20:13:06 +0200, Javier Carrasco wrote:
> This series adds the const modifier to the remaining regmap_config
> structs in the regulator subsystem that are effectively used as const
> (i.e., only read after their declaration), but kept ad writtable data.
> 
> 

Applied to

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

Thanks!

[1/2] regulator: da9121: Constify struct regmap_config
      commit: 05db2e27b92302a43f996561dbb58ecabc3cc85d
[2/2] regulator: max77857: Constify struct regmap_config
      commit: 32d1171014a74c788218e0a8a5fd6fef65fb10ba

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