On February 26, 2018 4:56:06 PM PST, Andrew Lunn <[email protected]> wrote: >commit f5e64032a799 ("net: phy: fix resume handling") changes the >locking semantics for phy_resume() such that the caller now needs to >hold the phy mutex. Not all call sites were adopted to this new >semantic, resulting in warnings from the added >WARN_ON(!mutex_is_locked(&phydev->lock)). Rather than change the >semantics, add a __phy_resume() and restore the old behavior of >phy_resume(). > >Reported-by: Heiner Kallweit <[email protected]> >Fixes: f5e64032a799 ("net: phy: fix resume handling") >Signed-off-by: Andrew Lunn <[email protected]> >--- >v2: Fix type in phy_resume() calling itself >---
This version looks good thanks for taking care of that: Reviewed-by: Florian Fainelli <[email protected]> -- Florian
