All of lore.kernel.org
 help / color / mirror / Atom feed
From: Libo Chen <clbchenlibo.chen@huawei.com>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Cc: balbi@ti.com, gregkh@linuxfoundation.org,
	grant.likely@linaro.org, rob.herring@calxeda.com,
	Li Zefan <lizefan@huawei.com>,
	linux-usb@vger.kernel.org, linux-omap@vger.kernel.org,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] usb: omap2430: fix memleak in err case
Date: Wed, 29 May 2013 10:47:36 +0800	[thread overview]
Message-ID: <51A56C48.5000501@huawei.com> (raw)
In-Reply-To: <51A4EC0A.2060506@cogentembedded.com>

On 2013/5/29 1:40, Sergei Shtylyov wrote:
> Hello.
> 
> On 22-05-2013 7:30, Libo Chen wrote:
> 
>> when omap_get_control_dev faild, we should release related platform_device
> 
>> * Changelog from v1:
>>     * fix spell: s/fail/fails/, s/relational/related/ , thank Sergei <sergei.shtylyov@cogentembedded.com>
> 
>    It seems you've actually replaced "fail" with "faild", not "fails".

sorry for my weak spell.


thanks again,

Libo


> 
>> Signed-off-by: Libo Chen <libo.chen@huawei.com>
>> ---
>>   drivers/usb/musb/omap2430.c |    3 ++-
>>   1 files changed, 2 insertions(+), 1 deletions(-)
> 
> WBR, Sergei
> 
> 
> 

WARNING: multiple messages have this Message-ID (diff)
From: Libo Chen <clbchenlibo.chen@huawei.com>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Cc: <balbi@ti.com>, <gregkh@linuxfoundation.org>,
	<grant.likely@linaro.org>, <rob.herring@calxeda.com>,
	Li Zefan <lizefan@huawei.com>, <linux-usb@vger.kernel.org>,
	<linux-omap@vger.kernel.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] usb: omap2430: fix memleak in err case
Date: Wed, 29 May 2013 10:47:36 +0800	[thread overview]
Message-ID: <51A56C48.5000501@huawei.com> (raw)
In-Reply-To: <51A4EC0A.2060506@cogentembedded.com>

On 2013/5/29 1:40, Sergei Shtylyov wrote:
> Hello.
> 
> On 22-05-2013 7:30, Libo Chen wrote:
> 
>> when omap_get_control_dev faild, we should release related platform_device
> 
>> * Changelog from v1:
>>     * fix spell: s/fail/fails/, s/relational/related/ , thank Sergei <sergei.shtylyov@cogentembedded.com>
> 
>    It seems you've actually replaced "fail" with "faild", not "fails".

sorry for my weak spell.


thanks again,

Libo


> 
>> Signed-off-by: Libo Chen <libo.chen@huawei.com>
>> ---
>>   drivers/usb/musb/omap2430.c |    3 ++-
>>   1 files changed, 2 insertions(+), 1 deletions(-)
> 
> WBR, Sergei
> 
> 
> 



  reply	other threads:[~2013-05-29  2:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-15  1:35 [PATCH] usb: omap2430: fix memleak in err case Libo Chen
2013-05-15  1:35 ` Libo Chen
2013-05-15 11:55 ` Sergei Shtylyov
2013-05-17  4:49   ` Libo Chen
2013-05-17  4:49     ` Libo Chen
2013-05-22  3:30 ` [PATCH v2] " Libo Chen
2013-05-22  3:30   ` Libo Chen
2013-05-28 12:41   ` Libo Chen
2013-05-28 12:41     ` Libo Chen
2013-05-28 15:34     ` Andy Shevchenko
2013-05-29  0:52       ` Libo Chen
2013-05-29  0:52         ` Libo Chen
2013-05-28 17:40   ` Sergei Shtylyov
2013-05-29  2:47     ` Libo Chen [this message]
2013-05-29  2:47       ` Libo Chen

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=51A56C48.5000501@huawei.com \
    --to=clbchenlibo.chen@huawei.com \
    --cc=balbi@ti.com \
    --cc=grant.likely@linaro.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=lizefan@huawei.com \
    --cc=rob.herring@calxeda.com \
    --cc=sergei.shtylyov@cogentembedded.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.