On February 26, 2018 4:56:06 PM PST, Andrew Lunn <and...@lunn.ch> 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 <hkallwe...@gmail.com>
>Fixes: f5e64032a799 ("net: phy: fix resume handling")
>Signed-off-by: Andrew Lunn <and...@lunn.ch>
>---
>v2: Fix type in phy_resume() calling itself
>---
This version looks good thanks for taking care of that:
Reviewed-by: Florian Fainelli <f.faine...@gmail.com>
--
Florian
