linux-kernel - Re: [PATCH] regmap: regmap_multi_reg

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: <173393655818.519837.3526009062975748002.b4-ty@kernel.org>
Date: Wed, 11 Dec 2024 17:02:38 +0000
From: Mark Brown <broonie@...nel.org>
To: Richard Fitzgerald <rf@...nsource.cirrus.com>
Cc: linux-kernel@...r.kernel.org, patches@...nsource.cirrus.com
Subject: Re: [PATCH] regmap: regmap_multi_reg_read(): make register list
 const

On Wed, 11 Dec 2024 13:35:58 +0000, Richard Fitzgerald wrote:
> Mark the list of registers passed into regmap_multi_reg_read() as a
> pointer to const. This allows the caller to define the register list
> as const data.
> 
> This requires making the same change to _regmap_bulk_read(), which is
> called by regmap_multi_reg_read().
> 
> [...]

Applied to

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

Thanks!

[1/1] regmap: regmap_multi_reg_read(): make register list const
      commit: eb708cd631a8dca17ff004ccc39bbeb096c1db22

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