From: Vitaly Kuzmichev <vkuzmichev@mvista.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] USB-CDC: wrong ep status used
Date: Fri, 13 Aug 2010 13:16:05 +0400 [thread overview]
Message-ID: <4C650D55.1080603@mvista.com> (raw)
In-Reply-To: <4C6429F1.7080304@mvista.com>
Hi Sergei,
On 08/12/2010 09:05 PM, Sergei Shtylyov wrote:
> Hello.
>
> Stefano Babic wrote:
>
>>> We get oops here!
>
>> Agree, and the issue is not related to this patch, I missed to correct
>> it, thanks. If no one complains, I will send a single patch to fix both
>> problems (wrong ep status + null pointer access).
>
> Looks like Vitaly has done the same already:
>
Yes, but I have not seen Stefano's comment when sent.
Stefano,
I would like to add you 'signed-off' in this patch because I took this
part from your patch:
- usb_ep_free_request (gadget->ep0, dev->req);
+ usb_ep_free_request (dev->status_ep, dev->req);
Do you allow me to add your signature?
next prev parent reply other threads:[~2010-08-13 9:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-11 21:41 [U-Boot] [PATCH] USB-CDC: wrong ep status used Stefano Babic
2010-08-12 10:13 ` Vitaly Kuzmichev
2010-08-12 12:28 ` Stefano Babic
2010-08-12 17:05 ` Sergei Shtylyov
2010-08-13 9:16 ` Vitaly Kuzmichev [this message]
2010-08-13 9:19 ` Stefano Babic
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=4C650D55.1080603@mvista.com \
--to=vkuzmichev@mvista.com \
--cc=u-boot@lists.denx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox