linux-kernel - Re: (subset) [PATCH V2] mfd: syscon: Use regmap max_register_is

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: <172770742318.523866.16912261914335612487.b4-ty@kernel.org>
Date: Mon, 30 Sep 2024 15:43:43 +0100
From: Lee Jones <lee@...nel.org>
To: Lee Jones <lee@...nel.org>, Nishanth Menon <nm@...com>
Cc: Arnd Bergmann <arnd@...db.de>, linux-arm-kernel@...ts.infradead.org, 
 linux-kernel@...r.kernel.org, Mark Brown <broonie@...nel.org>, 
 Shawn Guo <shawnguo@...nel.org>, linux-arm-msm@...r.kernel.org, 
 Bjorn Andersson <andersson@...nel.org>, 
 bcm-kernel-feedback-list@...adcom.com, 
 Florian Fainelli <florian.fainelli@...adcom.com>, 
 linux-stm32@...md-mailman.stormreply.com, 
 Alexandre Torgue <alexandre.torgue@...s.st.com>
Subject: Re: (subset) [PATCH V2] mfd: syscon: Use regmap max_register_is_0
 as needed

On Tue, 03 Sep 2024 13:47:10 -0500, Nishanth Menon wrote:
> syscon has always set the optional max_register configuration of
> regmap to ensure the correct checks are in place. However, a recent
> commit 0ec74ad3c157 ("regmap: rework ->max_register handling")
> introduced explicit configuration in regmap framework for register
> maps that is exactly 1 register, when max_register is pointing to a
> valid register 0. This commit solved a previous limitation of regmap
> framework.
> 
> [...]

Applied, thanks!

[1/1] mfd: syscon: Use regmap max_register_is_0 as needed
      commit: bf5b2ddf06da57fa623c11d599697a98f1007752

--
Lee Jones [李琼斯]