[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+7wUsyXMPu05mz4Mi6ELF=PJGLp82DTMFOHTZmQ2OHX_TdjWw@mail.gmail.com>
Date: Wed, 20 Jul 2016 08:03:03 +0200
From: Mathieu Malaterre <mathieu.malaterre@...il.com>
To: Rob Herring <robh+dt@...nel.org>
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 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 ?
Thx
--
Mathieu
Powered by blists - more mailing lists