A previous patch in the series reduces the number of  callsites of
dwc3_gadget_init_hw_endpoints from two to one. This patch removes the
redundant step of wrappering one function in the other, which can be done
by adding a parameter to dwc3_gadget_init_endpoints and moving the
linked-list initialization of dwc->gadet.ep_list.

Signed-off-by: Bryan O'Donoghue <pure.lo...@nexus-software.ie>
---
 drivers/usb/dwc3/gadget.c | 13 ++++---------
 1 file changed, 4 insertions(+), 9 deletions(-)

diff --git a/drivers/usb/dwc3/gadget.c b/drivers/usb/dwc3/gadget.c
index ef86ab6..574d795 100644
--- a/drivers/usb/dwc3/gadget.c
+++ b/drivers/usb/dwc3/gadget.c
@@ -1930,12 +1930,14 @@ static const struct usb_gadget_ops dwc3_gadget_ops = {
 
 /* -------------------------------------------------------------------------- 
*/
 
-static int dwc3_gadget_init_hw_endpoints(struct dwc3 *dwc, u8 num)
+static int dwc3_gadget_init_endpoints(struct dwc3 *dwc, u8 num)
 {
        struct dwc3_ep                  *dep;
        u8                              epnum;
        bool                            direction = false;
 
+       INIT_LIST_HEAD(&dwc->gadget.ep_list);
+
        for (epnum = 0; epnum < num; epnum++) {
 
                dep = kzalloc(sizeof(*dep), GFP_KERNEL);
@@ -2037,13 +2039,6 @@ static int dwc3_gadget_init_hw_endpoints(struct dwc3 
*dwc, u8 num)
        return 0;
 }
 
-static int dwc3_gadget_init_endpoints(struct dwc3 *dwc)
-{
-       INIT_LIST_HEAD(&dwc->gadget.ep_list);
-
-       return dwc3_gadget_init_hw_endpoints(dwc, dwc->num_eps);
-}
-
 static void dwc3_gadget_free_endpoints(struct dwc3 *dwc)
 {
        struct dwc3_ep                  *dep;
@@ -3151,7 +3146,7 @@ int dwc3_gadget_init(struct dwc3 *dwc)
         * sure we're starting from a well known location.
         */
 
-       ret = dwc3_gadget_init_endpoints(dwc);
+       ret = dwc3_gadget_init_endpoints(dwc, dwc->num_eps);
        if (ret)
                goto err6;
 
-- 
2.7.4

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

Reply via email to