linux-kernel - Re: [PATCH] regmap: Load register defaults in blocks rather than register by register

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <168492836798.52206.9285339967466812417.b4-ty@kernel.org>
Date:   Wed, 24 May 2023 12:39:27 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Mark Brown <broonie@...nel.org>
Cc:     linux-kernel@...r.kernel.org
Subject: Re: [PATCH] regmap: Load register defaults in blocks rather than
 register by register

On Tue, 23 May 2023 22:22:27 +0100, Mark Brown wrote:
> Currently we use the normal single register write function to load the
> default values into the cache, resulting in a large number of reallocations
> when there are blocks of registers as we extend the memory region we are
> using to store the values. Instead scan through the list of defaults for
> blocks of adjacent registers and do a single allocation and insert for each
> such block. No functional change.
> 
> [...]

Applied to

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

Thanks!

[1/1] regmap: Load register defaults in blocks rather than register by register
      commit: 3a48d2127f4dbd767d43bf8280b67d585e701f75

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