[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <7bde400c-add3-47c7-bbbf-311aa8270ccf@lunn.ch>
Date: Tue, 27 May 2025 15:14:56 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Christophe JAILLET <christophe.jaillet@...adoo.fr>
Cc: 李哲 <sensor1010@....com>, andrew+netdev@...n.ch,
davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org,
pabeni@...hat.com, mcoquelin.stm32@...il.com,
alexandre.torgue@...s.st.com, jonas@...boo.se,
rmk+kernel@...linux.org.uk, david.wu@...k-chips.com, wens@...e.org,
jan.petrous@....nxp.com, netdev@...r.kernel.org,
linux-stm32@...md-mailman.stormreply.com,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] net: dwmac-rk: No need to check the return value of the
phy_power_on()
On Tue, May 27, 2025 at 07:43:57AM +0200, Christophe JAILLET wrote:
> Le 26/05/2025 à 18:16, 李哲 a écrit :
> > since the return value of the phy_power_on() function is always 0,
> > checking its return value is redundant.
>
> Can you elaborate why?
>
> Looking at (1], I think that it is obvious that non-0 values can be
> returned.
Wrong phy_power_on(). There is a local scope one within the driver.
Andrew
Powered by blists - more mailing lists