From: Libo Chen <clbchenlibo.chen@huawei.com>
To: Chris Metcalf <cmetcalf@tilera.com>
Cc: Libo Chen <libo.chen@huawei.com>, <stern@rowland.harvard.edu>,
<grant.likely@linaro.org>, <rob.herring@calxeda.com>,
<linux-usb@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<akpm@linux-foundation.org>, <lizefan@huawei.com>
Subject: Re: [PATCH RESEND 4/4] usb: tilegx: fix memleak when create hcd fail
Date: Fri, 10 May 2013 09:50:46 +0800 [thread overview]
Message-ID: <518C5276.5090904@huawei.com> (raw)
In-Reply-To: <518C48AF.6070701@huawei.com>
On 2013/5/10 9:09, Libo Chen wrote:
> On 2013/5/10 2:02, Chris Metcalf wrote:
>> On 5/9/2013 2:08 AM, Libo Chen wrote:
>>> When usb_create_hcd fail, we should call gxio_usb_host_destroy
>>>
>>> Signed-off-by: Libo Chen <libo.chen@huawei.com>
>>> ---
>>> drivers/usb/host/ohci-tilegx.c | 7 +++++--
>>> 1 files changed, 5 insertions(+), 2 deletions(-)
>>
>> Thanks; taken into the tile tree. I also made the same change to ehci-tilegx.c.
>>
>
> Hi Chris,
>
> Thanks reply, May be I miss. Please ignore this patch.
Sorry, this patch is ok, no problem.
>
>
>
> .
>
next prev parent reply other threads:[~2013-05-10 1:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-09 6:05 [PATCH RESEND 0/4] usb: fix four memleak Libo Chen
2013-05-09 6:05 ` [PATCH RESEND 1/4] usb: ehci-s5p: fix memleak when devm_usb_get_phy fail Libo Chen
2013-05-09 19:29 ` Alan Stern
2013-05-09 6:05 ` [PATCH RESEND 2/4] usb: isp1760-if: fix memleak when platform_get_resource fail Libo Chen
2013-05-09 6:05 ` [PATCH RESEND 3/4] usb: ohci: fix goto wrong tag in err case Libo Chen
2013-05-09 19:27 ` Alan Stern
2013-05-09 6:05 ` [PATCH RESEND 4/4] usb: tilegx: fix memleak when create hcd fail Libo Chen
2013-05-09 18:02 ` Chris Metcalf
2013-05-10 1:09 ` Libo Chen
2013-05-10 1:50 ` Libo Chen [this message]
2013-05-09 19:29 ` Alan Stern
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=518C5276.5090904@huawei.com \
--to=clbchenlibo.chen@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=cmetcalf@tilera.com \
--cc=grant.likely@linaro.org \
--cc=libo.chen@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=rob.herring@calxeda.com \
--cc=stern@rowland.harvard.edu \
/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.