This commit forces callers of phy_resume() and phy_suspend() to hold mutex phydev->lock. This was done for calls to phy_resume() and phy_suspend() in phylib, however there are more callers in network drivers. I'd assume that these other calls issue a warning now because of the lock not being held. So is there something I miss or would this have to be fixed?
- Potential issue with f5e64032a799 "net: phy:... Heiner Kallweit
- Re: Potential issue with f5e64032a799 "... Andrew Lunn
- Re: Potential issue with f5e64032a799 &q... Heiner Kallweit
- Re: Potential issue with f5e64032a79... Florian Fainelli
- Re: Potential issue with f5e6403... Heiner Kallweit
- Re: Potential issue with f5... Russell King - ARM Linux
- Re: Potential issue wit... Andrew Lunn
- Re: handling of phy_stop() and p... Heiner Kallweit
- Re: handling of phy_stop() ... Russell King - ARM Linux
- Re: handling of phy_sto... Florian Fainelli
