All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Baldyga <r.baldyga@samsung.com>
To: balbi@ti.com, paulz@synopsys.com
Cc: gregkh@linuxfoundation.org, linux-usb@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] usb: dwc2: fix the uncompleted requests problem
Date: Tue, 20 Jan 2015 07:12:42 +0100	[thread overview]
Message-ID: <54BDF1DA.6070507@samsung.com> (raw)
In-Reply-To: <1420450295-25818-1-git-send-email-r.baldyga@samsung.com>

Hi Felipe,

I can't see these patches in your tree. I see only "usb: dwc2: gadget:
kill requests with 'force' in s3c_hsotg_udc_stop()", which doesn't fix
the bug completely. I was sure that my the final patch was in your tree,
so what happened? Can you apply these patches to fix this problem?

On 01/05/2015 10:31 AM, Robert Baldyga wrote:
> Hi Felipe,
> 
> I prepared this patchset in response to our discussion:
> https://lkml.org/lkml/2014/12/29/193
> 
> It reverts of unproper patch and adds working solution of the problem
> described in commit messages.
> 
> Best regards,
> Robert Baldyga
> 
> Robert Baldyga (2):
>   Revert "usb: dwc2: gadget: kill requests with 'force' in
>     s3c_hsotg_udc_stop()"
>   drivers: usb: dwc2: remove 'force' parameter from kill_all_requests()
> 
>  drivers/usb/dwc2/gadget.c | 31 ++++++++++---------------------
>  1 file changed, 10 insertions(+), 21 deletions(-)
> 

Best regards,
Robert Baldyga

      parent reply	other threads:[~2015-01-20  6:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-05  9:31 [PATCH 0/2] usb: dwc2: fix the uncompleted requests problem Robert Baldyga
2015-01-05  9:31 ` [PATCH 1/2] Revert "usb: dwc2: gadget: kill requests with 'force' in s3c_hsotg_udc_stop()" Robert Baldyga
2015-01-05  9:31 ` [PATCH 2/2] drivers: usb: dwc2: remove 'force' parameter from kill_all_requests() Robert Baldyga
2015-01-27 15:42   ` Felipe Balbi
2015-01-28  7:18     ` Robert Baldyga
2015-01-28 14:08       ` Felipe Balbi
2015-01-20  6:12 ` Robert Baldyga [this message]

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=54BDF1DA.6070507@samsung.com \
    --to=r.baldyga@samsung.com \
    --cc=balbi@ti.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=paulz@synopsys.com \
    /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.