linux-kernel - Re: [PATCH] rtc: cmos: Fix return value of nvmem callbacks

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]

Date: Fri, 21 Jun 2024 07:23:25 +0100
From: Srinivas Kandagatla <srinivas.kandagatla@...aro.org>
To: Alexandre Belloni <alexandre.belloni@...tlin.com>, 
 Dan Carpenter <dan.carpenter@...aro.org>, 
 Joy Chakraborty <joychakr@...gle.com>
Cc: linux-rtc@...r.kernel.org, linux-kernel@...r.kernel.org, 
 stable@...r.kernel.org
Subject: Re: [PATCH] rtc: cmos: Fix return value of nvmem callbacks


On Wed, 12 Jun 2024 08:36:35 +0000, Joy Chakraborty wrote:
> Read/write callbacks registered with nvmem core expect 0 to be returned
> on success and a negative value to be returned on failure.
> 
> cmos_nvram_read()/cmos_nvram_write() currently return the number of
> bytes read or written, fix to return 0 on success and -EIO incase number
> of bytes requested was not read or written.
> 
> [...]

Applied, thanks!

[1/1] rtc: cmos: Fix return value of nvmem callbacks
      commit: ac9b2633e85f6b53cf368f90ae7589553e8998b6

Best regards,
-- 
Srinivas Kandagatla <srinivas.kandagatla@...aro.org>