From: Libo Chen <clbchenlibo.chen@huawei.com>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Cc: <grant.likely@linaro.org>, <rob.herring@calxeda.com>,
<linux-mips@linux-mips.org>, LKML <linux-kernel@vger.kernel.org>,
<devicetree-discuss@lists.ozlabs.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] usb: omap2430: fix memleak in err case
Date: Fri, 17 May 2013 12:49:26 +0800 [thread overview]
Message-ID: <5195B6D6.7030504@huawei.com> (raw)
In-Reply-To: <519377C4.1040800@cogentembedded.com>
On 2013/5/15 19:55, Sergei Shtylyov wrote:
> Hello.
>
> On 15-05-2013 5:35, Libo Chen wrote:
>
>> when omap_get_control_dev fail, we should release relational platform_device
>
> s/fail/fails/, s/relational/related/?
>
>> Signed-off-by: Libo Chen <libo.chen@huawei.com>
>
> You've posted this to the wrong mailing list, linux-mips; devicetree-discuss also seems hardly related.
>
> WBR, Sergei
>
>
>
Hi Sergei,
Thank you for your remind.
WARNING: multiple messages have this Message-ID (diff)
From: Libo Chen <clbchenlibo.chen@huawei.com>
To: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Cc: grant.likely@linaro.org, rob.herring@calxeda.com,
linux-mips@linux-mips.org, LKML <linux-kernel@vger.kernel.org>,
devicetree-discuss@lists.ozlabs.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] usb: omap2430: fix memleak in err case
Date: Fri, 17 May 2013 12:49:26 +0800 [thread overview]
Message-ID: <5195B6D6.7030504@huawei.com> (raw)
Message-ID: <20130517044926.xLXd9tkkjpwAqtCZ9siaO-NpK6kHOSU8i5PASYnEqro@z> (raw)
In-Reply-To: <519377C4.1040800@cogentembedded.com>
On 2013/5/15 19:55, Sergei Shtylyov wrote:
> Hello.
>
> On 15-05-2013 5:35, Libo Chen wrote:
>
>> when omap_get_control_dev fail, we should release relational platform_device
>
> s/fail/fails/, s/relational/related/?
>
>> Signed-off-by: Libo Chen <libo.chen@huawei.com>
>
> You've posted this to the wrong mailing list, linux-mips; devicetree-discuss also seems hardly related.
>
> WBR, Sergei
>
>
>
Hi Sergei,
Thank you for your remind.
next prev parent reply other threads:[~2013-05-17 4:50 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 [this message]
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
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=5195B6D6.7030504@huawei.com \
--to=clbchenlibo.chen@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--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.