linux-kernel - Re: [RFC] regmap: rework ->max

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: <170715521846.847227.12922920543306914597.b4-ty@kernel.org>
Date: Mon, 05 Feb 2024 17:46:58 +0000
From: Mark Brown <broonie@...nel.org>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>, 
 "Rafael J. Wysocki" <rafael@...nel.org>, linux-kernel@...r.kernel.org, 
 Jan Dakinevich <jan.dakinevich@...utedevices.com>
Cc: kernel@...utedevices.com
Subject: Re: [RFC] regmap: rework ->max_register handling

On Fri, 26 Jan 2024 23:08:36 +0300, Jan Dakinevich wrote:
> When regmap consists of single register, 'regmap' subsystem is unable to
> understand whether ->max_register is set or not, because in both cases it
> is equal to zero. It leads to that the logic based on value of
> ->max_register doesn't work. For example using of REGCACHE_FLAT fails.
> 
> This patch introduces an extra parameter to regmap config, indicating
> that zero value in ->max_register is authentic.
> 
> [...]

Applied to

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

Thanks!

[1/1] regmap: rework ->max_register handling
      commit: 0ec74ad3c157bd4bcbcc8b294777733687e8cd2a

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