udc-core provides a better way to handle release
methods, let's use it.

Signed-off-by: Felipe Balbi <[email protected]>
---
 drivers/usb/gadget/fsl_udc_core.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/drivers/usb/gadget/fsl_udc_core.c 
b/drivers/usb/gadget/fsl_udc_core.c
index 4d5ff23..f224169 100644
--- a/drivers/usb/gadget/fsl_udc_core.c
+++ b/drivers/usb/gadget/fsl_udc_core.c
@@ -2493,7 +2493,6 @@ static int __init fsl_udc_probe(struct platform_device 
*pdev)
 
        /* Setup gadget.dev and register with kernel */
        dev_set_name(&udc_controller->gadget.dev, "gadget");
-       udc_controller->gadget.dev.release = fsl_udc_release;
        udc_controller->gadget.dev.of_node = pdev->dev.of_node;
 
        if (!IS_ERR_OR_NULL(udc_controller->transceiver))
@@ -2530,7 +2529,8 @@ static int __init fsl_udc_probe(struct platform_device 
*pdev)
                goto err_free_irq;
        }
 
-       ret = usb_add_gadget_udc(&pdev->dev, &udc_controller->gadget);
+       ret = usb_add_gadget_udc_release(&pdev->dev, &udc_controller->gadget,
+                       fsl_udc_release);
        if (ret)
                goto err_del_udc;
 
-- 
1.8.1.rc1.5.g7e0651a

--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to