[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <f9d9860c-0446-faea-2a69-0b2516ba7dcf@nfschina.com>
Date: Fri, 20 Oct 2023 10:59:41 +0800
From: Su Hui <suhui@...china.com>
To: Dan Carpenter <dan.carpenter@...aro.org>
Cc: woojung.huh@...rochip.com, UNGLinuxDriver@...rochip.com,
davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org,
pabeni@...hat.com, nathan@...nel.org, ndesaulniers@...gle.com,
trix@...hat.com, netdev@...r.kernel.org, linux-usb@...r.kernel.org,
linux-kernel@...r.kernel.org, llvm@...ts.linux.dev,
kernel-janitors@...r.kernel.org
Subject: Re: [PATCH] net: lan78xx: add an error code check in
lan78xx_write_raw_eeprom
On 2023/10/19 18:34, Dan Carpenter wrote:
> On Thu, Oct 19, 2023 at 04:40:23PM +0800, Su Hui wrote:
>> check the value of 'ret' after call 'lan78xx_read_reg'.
>>
>> Signed-off-by: Su Hui <suhui@...china.com>
>> ---
>>
>> Clang complains that value stored to 'ret' is never read.
>> Maybe this place miss an error code check, I'm not sure
>> about this.
> There are a bunch more "ret = " assignments which aren't used in this
> function.
Yep, same problemĀ exists at lan78xx_read_raw_eeprom().
I try to send v2 patch to fix this.
Su Hui
Powered by blists - more mailing lists