Re: [PATCH net-next] net: phy: Deal with unbound PHY driver in phy_attached_print()

2017-08-22 Thread David Miller
From: Florian Fainelli Date: Tue, 22 Aug 2017 14:45:44 -0700 > On 08/22/2017 02:44 PM, David Miller wrote: >> From: Florian Fainelli >> Date: Tue, 22 Aug 2017 14:26:47 -0700 >> >>> Priit reported that stmmac was crashing with the trace below. This is >>> because >>> phy_attached_print() is cal

Re: [PATCH net-next] net: phy: Deal with unbound PHY driver in phy_attached_print()

2017-08-22 Thread Florian Fainelli
On 08/22/2017 02:44 PM, David Miller wrote: > From: Florian Fainelli > Date: Tue, 22 Aug 2017 14:26:47 -0700 > >> Priit reported that stmmac was crashing with the trace below. This is because >> phy_attached_print() is called too early right after the PHY device has been >> found, but before it h

Re: [PATCH net-next] net: phy: Deal with unbound PHY driver in phy_attached_print()

2017-08-22 Thread David Miller
From: Florian Fainelli Date: Tue, 22 Aug 2017 14:26:47 -0700 > Priit reported that stmmac was crashing with the trace below. This is because > phy_attached_print() is called too early right after the PHY device has been > found, but before it has a driver attached, since that is only done in > ph

[PATCH net-next] net: phy: Deal with unbound PHY driver in phy_attached_print()

2017-08-22 Thread Florian Fainelli
Priit reported that stmmac was crashing with the trace below. This is because phy_attached_print() is called too early right after the PHY device has been found, but before it has a driver attached, since that is only done in phy_probe() which occurs later. Fix this by dealing with a possibly NULL