All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Michael Grzeschik <m.grzeschik@pengutronix.de>
Cc: linux-usb@vger.kernel.org, balbi@kernel.org, kernel@pengutronix.de
Subject: Re: [PATCH v3] usb: dwc3: gadget: move cmd_endtransfer to extra function
Date: Sun, 6 Mar 2022 14:57:17 +0100	[thread overview]
Message-ID: <YiS9vZWoONJKTbpL@kroah.com> (raw)
In-Reply-To: <20220305005356.1400365-1-m.grzeschik@pengutronix.de>

On Sat, Mar 05, 2022 at 01:53:56AM +0100, Michael Grzeschik wrote:
> This patch adds the extra function __dwc3_stop_active_transfer to
> consolidate the same codepath.
> 
> Signed-off-by: Michael Grzeschik <m.grzeschik@pengutronix.de>
> 
> ---
> v1 -> v2: - renamed the function to __dwc3_stop_active_transfer
>           - added function description
> v2 -> v3: - fixed spelling and removed extra line
> 	  - make __dwc3_stop_active_transfer return ret
> 	  - use ret in __dwc3_gadget_start_isoc

So is this v3 of a single patch in this series, or the whole series?

I'm totally confused, please resend the whole, updated series, as v4
please.

thanks,

greg k-h

  reply	other threads:[~2022-03-06 13:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-28 15:08 [PATCH 0/3] usb: dwc3: gadget: simple refactoring patches Michael Grzeschik
2022-02-28 15:08 ` [PATCH 1/3] usb: dwc3: gadget: ep_queue simplify isoc start condition Michael Grzeschik
2022-03-02  1:24   ` Thinh Nguyen
2022-02-28 15:08 ` [PATCH 2/3] usb: dwc3: gadget: move cmd_endtransfer to extra function Michael Grzeschik
2022-03-02  1:22   ` Thinh Nguyen
2022-03-03 13:11     ` [PATCH v2] " Michael Grzeschik
2022-03-04  2:26       ` Thinh Nguyen
2022-03-05  0:53         ` [PATCH v3] " Michael Grzeschik
2022-03-06 13:57           ` Greg KH [this message]
2022-02-28 15:08 ` [PATCH 3/3] usb: dwc3: gadget: EP_DELAY_START is only handled for non isoc eps Michael Grzeschik
2022-03-01  1:12   ` Thinh Nguyen
2022-03-01 21:06     ` Michael Grzeschik

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YiS9vZWoONJKTbpL@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=balbi@kernel.org \
    --cc=kernel@pengutronix.de \
    --cc=linux-usb@vger.kernel.org \
    --cc=m.grzeschik@pengutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.