linux-kernel - Re: (subset) [PATCH] mfd: bd718x7: Use regmap_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: <176244496453.1924614.12838084027318818785.b4-ty@kernel.org>
Date: Thu, 06 Nov 2025 16:02:44 +0000
From: Lee Jones <lee@...nel.org>
To: Matti Vaittinen <mazziesaccount@...il.com>, 
 Matti Vaittinen <mazziesaccount@...il.com>
Cc: Lee Jones <lee@...nel.org>, linux-kernel@...r.kernel.org
Subject: Re: (subset) [PATCH] mfd: bd718x7: Use regmap_reg_range()

On Mon, 27 Oct 2025 14:12:06 +0200, Matti Vaittinen wrote:
> Initializing the regmap_ranges using direct assignment to the range_min
> and range_max members is a slightly verbose. In general we can make it a
> tad cleaner when using the regmap_reg_range() macro.
> 
> The rohm-bd718x7.c is doing this open-coded initialization. It's not
> really bad as there is only one range defined, but it is still worth
> converting it to use the regmap_reg_range() so no-one uses it as a bad
> example.
> 
> [...]

Applied, thanks!

[1/1] mfd: bd718x7: Use regmap_reg_range()
      commit: 1810b210872ffc9985febca0880702a7102aad31

--
Lee Jones [李琼斯]