Re: [PATCH] net: phy: Don't call phy_resume if phy_init_hw failed

2014-05-15 Thread David Miller
From: Guenter Roeck Date: Wed, 14 May 2014 13:12:49 -0700 > After the call to phy_init_hw failed in phy_attach_direct, phy_detach is > called > to detach the phy device from its network device. If the attached driver is a > generic phy driver, this also detaches the driver. Subsequently

Re: [PATCH] net: phy: Don't call phy_resume if phy_init_hw failed

2014-05-14 Thread Florian Fainelli
2014-05-14 13:12 GMT-07:00 Guenter Roeck : > After the call to phy_init_hw failed in phy_attach_direct, phy_detach is > called > to detach the phy device from its network device. If the attached driver is a > generic phy driver, this also detaches the driver. Subsequently phy_resume > is called,

[PATCH] net: phy: Don't call phy_resume if phy_init_hw failed

2014-05-14 Thread Guenter Roeck
After the call to phy_init_hw failed in phy_attach_direct, phy_detach is called to detach the phy device from its network device. If the attached driver is a generic phy driver, this also detaches the driver. Subsequently phy_resume is called, which assumes without checking that a driver is

[PATCH] net: phy: Don't call phy_resume if phy_init_hw failed

2014-05-14 Thread Guenter Roeck
After the call to phy_init_hw failed in phy_attach_direct, phy_detach is called to detach the phy device from its network device. If the attached driver is a generic phy driver, this also detaches the driver. Subsequently phy_resume is called, which assumes without checking that a driver is

Re: [PATCH] net: phy: Don't call phy_resume if phy_init_hw failed

2014-05-14 Thread Florian Fainelli
2014-05-14 13:12 GMT-07:00 Guenter Roeck li...@roeck-us.net: After the call to phy_init_hw failed in phy_attach_direct, phy_detach is called to detach the phy device from its network device. If the attached driver is a generic phy driver, this also detaches the driver. Subsequently phy_resume