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
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,
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
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
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
5 matches
Mail list logo