[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <171895084703.13918.2428522284763807031.b4-ty@linaro.org>
Date: Fri, 21 Jun 2024 07:20:47 +0100
From: Srinivas Kandagatla <srinivas.kandagatla@...aro.org>
To: Jerome Brunet <jbrunet@...libre.com>,
Martin Blumenstingl <martin.blumenstingl@...glemail.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Dan Carpenter <dan.carpenter@...aro.org>,
Joy Chakraborty <joychakr@...gle.com>
Cc: linux-arm-kernel@...ts.infradead.org, linux-amlogic@...ts.infradead.org,
linux-kernel@...r.kernel.org, stable@...r.kernel.org
Subject: Re: [PATCH] nvmem: meson-efuse: Fix return value of nvmem
callbacks
On Tue, 11 Jun 2024 14:55:24 +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.
>
> meson_efuse_read() and meson_efuse_write() call into
> meson_sm_call_read() and meson_sm_call_write() respectively which return
> the number of bytes read or written on success as per their api
> description.
>
> [...]
Applied, thanks!
[1/1] nvmem: meson-efuse: Fix return value of nvmem callbacks
commit: c87ba397647e1ad84d2771461a6035a63d388198
Best regards,
--
Srinivas Kandagatla <srinivas.kandagatla@...aro.org>
Powered by blists - more mailing lists