Le 23/11/2016 à 13:39, woojung@microchip.com a écrit :
> From: Woojung Huh
>
> When phy_init_hw() fails at phy_attach_direct();
> - phy_detach() calls phy_led_triggers_unregister() without
> previous call of phy_led_triggers_register().
> - still call phy_led_triggers_register() and cause
On Wed, Nov 23, 2016 at 09:39:37PM +, woojung@microchip.com wrote:
> From: Woojung Huh
>
> When phy_init_hw() fails at phy_attach_direct();
> - phy_detach() calls phy_led_triggers_unregister() without
> previous call of phy_led_triggers_register().
> - still call phy_led_triggers_regis
Hello.
On 11/24/2016 12:39 AM, woojung@microchip.com wrote:
From: Woojung Huh
When phy_init_hw() fails at phy_attach_direct();
- phy_detach() calls phy_led_triggers_unregister() without
previous call of phy_led_triggers_register().
- still call phy_led_triggers_register() and cause memo
From: Woojung Huh
When phy_init_hw() fails at phy_attach_direct();
- phy_detach() calls phy_led_triggers_unregister() without
previous call of phy_led_triggers_register().
- still call phy_led_triggers_register() and cause memory leak.
Signed-off-by: Woojung Huh
---
drivers/net/phy/phy_devi