[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200519182916.GM624248@lunn.ch>
Date: Tue, 19 May 2020 20:29:16 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Jakub Kicinski <kuba@...nel.org>
Cc: Dan Murphy <dmurphy@...com>, f.fainelli@...il.com,
hkallweit1@...il.com, davem@...emloft.net, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, devicetree@...r.kernel.org
Subject: Re: [PATCH net-next 2/4] net: phy: dp83869: Set opmode from straps
On Tue, May 19, 2020 at 09:58:18AM -0700, Jakub Kicinski wrote:
> On Tue, 19 May 2020 09:18:11 -0500 Dan Murphy wrote:
> > If the op-mode for the device is not set in the device tree then set
> > the strapped op-mode and store it for later configuration.
> >
> > Signed-off-by: Dan Murphy <dmurphy@...com>
>
> ../drivers/net/phy/dp83869.c: In function0 dp83869_set_strapped_mode:
> ../drivers/net/phy/dp83869.c:171:10: warning: comparison is always false due to limited range of data type [-Wtype-limits]
> 171 | if (val < 0)
> | ^
Hi Jakub
This happens a lot with PHY drivers. The register being read is a u16,
so that is what people use.
Is this now a standard GCC warning? Or have you turned on extra
checking?
Andrew
Powered by blists - more mailing lists