linux-kernel - Re: [PATCH v1 1/1] regmap: irq: Use one way of setting all bits in the 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] [day] [month] [year] [list]

Message-ID: <Z6UGue-OUujUKYi6@smile.fi.intel.com>
Date: Thu, 6 Feb 2025 21:00:09 +0200
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: Mark Brown <broonie@...nel.org>
Cc: Matti Vaittinen <mazziesaccount@...il.com>,
	linux-kernel@...r.kernel.org,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	"Rafael J. Wysocki" <rafael@...nel.org>,
	Danilo Krummrich <dakr@...nel.org>
Subject: Re: [PATCH v1 1/1] regmap: irq: Use one way of setting all bits in
 the register

On Thu, Feb 06, 2025 at 04:51:35PM +0000, Mark Brown wrote:
> On Thu, Feb 06, 2025 at 06:29:33PM +0200, Andy Shevchenko wrote:
> > Currently there are two ways of how we represent all bits set, i.e.
> > UINT_MAX and GENMASK(31, 0). Use the latter as the single way of
> > doing that, which is crystal clear on how many bits we are talking
> > about.
> 
> I think I'd rather go to UINT_MAX since it's more obviously correct if
> we see platforms with int that isn't 32 bits.

Okay!

-- 
With Best Regards,
Andy Shevchenko