public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Libo Chen <clbchenlibo.chen@huawei.com>
To: Greg KH <greg@kroah.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>,
	Libo Chen <chenlibo.3@gmail.com>
Subject: Re: [PATCH 4/4] usb: tilegx: fix memleak when create hcd fail
Date: Fri, 17 May 2013 12:31:55 +0800	[thread overview]
Message-ID: <5195B2BB.3040602@huawei.com> (raw)
In-Reply-To: <20130517003428.GA10235@kroah.com>

Hi Greg,

On 2013/5/17 8:34, Greg KH wrote:
> On Thu, May 09, 2013 at 12:58:11PM +0800, Libo Chen wrote:
>> From: Libo Chen <chenlibo.3@gmail.com>
>>
>> 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(-)
> 
> This patch doesn't apply at all, care to refresh it?
> 
> thanks,
> 
> greg k-h
> 
> .

this patch has been merged to upstream by Chris Metcalf <cmetcalf@tilera.com>.
(commit: abab8761d095e0805879df48a8ba6ea7f8b31c5e)

thanks,
Libo


> 



      reply	other threads:[~2013-05-17  4:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-09  4:58 [PATCH 0/4] usb: fix four memleak Libo Chen
2013-05-09  4:58 ` [PATCH 1/4] usb: ehci-s5p: fix memleak when fallback to pdata Libo Chen
2013-05-09  4:58 ` [PATCH 2/4] usb: isp1760-if: fix memleak when platform_get_resource fail Libo Chen
2013-05-09  4:58 ` [PATCH 3/4] usb: ohci: fix goto wrong tag in err case Libo Chen
2013-05-17  0:34   ` Greg KH
2013-05-09  4:58 ` [PATCH 4/4] usb: tilegx: fix memleak when create hcd fail Libo Chen
2013-05-17  0:34   ` Greg KH
2013-05-17  4:31     ` Libo Chen [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=5195B2BB.3040602@huawei.com \
    --to=clbchenlibo.chen@huawei.com \
    --cc=akpm@linux-foundation.org \
    --cc=chenlibo.3@gmail.com \
    --cc=grant.likely@linaro.org \
    --cc=greg@kroah.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox