[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAL_JsqJaWky61QA0qdKozyriYpZiR2poY+U-7a9Latr7z_FoSA@mail.gmail.com>
Date: Fri, 22 Jul 2016 14:58:06 -0500
From: Rob Herring <robh+dt@...nel.org>
To: Mathieu Malaterre <mathieu.malaterre@...il.com>
Cc: Frank Rowand <frowand.list@...il.com>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
linuxppc-dev <linuxppc-dev@...ts.ozlabs.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3] of: fix memory leak related to safe_name()
On Wed, Jul 20, 2016 at 1:03 AM, Mathieu Malaterre
<mathieu.malaterre@...il.com> wrote:
> On Fri, Jun 24, 2016 at 10:38 PM, Rob Herring <robh+dt@...nel.org> wrote:
>> On Fri, Jun 17, 2016 at 2:51 AM, Mathieu Malaterre
>> <mathieu.malaterre@...il.com> wrote:
>>> v3 tested here multiple times ! memleak is now gone.
>>>
>>> Tested-by: Mathieu Malaterre <mathieu.malaterre@...il.com>
>>>
>>> Thanks
>>>
>>> On Thu, Jun 16, 2016 at 7:51 PM, Frank Rowand <frowand.list@...il.com> wrote:
>>>> From: Frank Rowand <frank.rowand@...sony.com>
>>>>
>>>> Fix a memory leak resulting from memory allocation in safe_name().
>>>> This patch fixes all call sites of safe_name().
>>
>> Applied, thanks.
>>
>> Rob
>
> Could this patch be considered for stable ?
Yes, I tagged it for stable. I didn't send it for 4.7, so it won't go
in until after 4.8-rc1 though.
Rob
Powered by blists - more mailing lists