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: <170924288521.1876058.17039410988641228858.b4-ty@bootlin.com>
Date: Thu, 29 Feb 2024 22:43:06 +0100
From: Alexandre Belloni <alexandre.belloni@...tlin.com>
To: Guenter Roeck <linux@...ck-us.net>, linux-rtc@...r.kernel.org,
	linux-kernel@...r.kernel.org,
	Antoniu Miclaus <antoniu.miclaus@...log.com>
Subject: Re: [PATCH] rtc: max31335: fix interrupt status reg

On Mon, 19 Feb 2024 11:16:15 +0200, Antoniu Miclaus wrote:
> Fix the register value comparison in the `max31335_volatile_reg`
> function for the interrupt status register.
> 
> MAX31335_STATUS1 macro definition corresponds to the actual
> interrupt status register.
> 
> 
> [...]

I hope you realize that this is exactly what Guenter was referring to
when he said:

"It seems to be quite common for automotive chips, though, that they are held
tightly under wrap, making it all but impossible to properly review their drivers.
I have observed several times now that information not available to reviewers
resulted in bad or buggy drivers."


Applied

[1/1] rtc: max31335: fix interrupt status reg
      https://git.kernel.org/abelloni/c/c12e67e076cb

Best regards,

-- 
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ