linux-kernel - Re: [PATCH] mfd: syscon: Set max_register_is_0 when syscon points to a single 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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <efac0d73-9a33-4851-9f66-7dae5bfc515f@sirena.org.uk>
Date: Wed, 28 Aug 2024 21:26:58 +0100
From: Mark Brown <broonie@...nel.org>
To: Nishanth Menon <nm@...com>
Cc: Arnd Bergmann <arnd@...db.de>, Lee Jones <lee@...nel.org>,
	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
	afd@...com, bb@...com, d-gole@...com,
	Jan Dakinevich <jan.dakinevich@...utedevices.com>
Subject: Re: [PATCH] mfd: syscon: Set max_register_is_0 when syscon points to
 a single register

On Wed, Aug 28, 2024 at 09:44:34AM -0500, Nishanth Menon wrote:

> This is a patch for syscon, not regmap. I am a bit confused as to what
> objection beyond the "Fixes" usage (which I can drop
> in a respin) you may have here, will appreciate if you are NAKing the
> patch and on what rationale.

> I understand that regmap considers the max_register usage entirely
> optional, but syscon does already use it (my patch doesn't introduce
> it). I am just getting syscon to catchup to what regmap already
> provides.

If you are absolutely confident that all syscon users know how big their
regmap is then modulo the claim that it's a fix for an unrelated patch
which doesn't change the behaviour for these regmaps at all then it's
fine.

Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)