On Wed, Jul 20, 2016 at 1:03 AM, Mathieu Malaterre
wrote:
> On Fri, Jun 24, 2016 at 10:38 PM, Rob Herring wrote:
>> On Fri, Jun 17, 2016 at 2:51 AM, Mathieu Malaterre
>> wrote:
>>> v3 tested here multiple times ! memleak is now gone.
>>>
>>> Tested-by: Mathieu Malaterre
>>>
>>> Thanks
>>>
>>> O
On Fri, Jun 24, 2016 at 10:38 PM, Rob Herring wrote:
> On Fri, Jun 17, 2016 at 2:51 AM, Mathieu Malaterre
> wrote:
>> v3 tested here multiple times ! memleak is now gone.
>>
>> Tested-by: Mathieu Malaterre
>>
>> Thanks
>>
>> On Thu, Jun 16, 2016 at 7:51 PM, Frank Rowand wrote:
>>> From: Frank R
On Fri, Jun 17, 2016 at 2:51 AM, Mathieu Malaterre
wrote:
> v3 tested here multiple times ! memleak is now gone.
>
> Tested-by: Mathieu Malaterre
>
> Thanks
>
> On Thu, Jun 16, 2016 at 7:51 PM, Frank Rowand wrote:
>> From: Frank Rowand
>>
>> Fix a memory leak resulting from memory allocation in
v3 tested here multiple times ! memleak is now gone.
Tested-by: Mathieu Malaterre
Thanks
On Thu, Jun 16, 2016 at 7:51 PM, Frank Rowand wrote:
> From: Frank Rowand
>
> Fix a memory leak resulting from memory allocation in safe_name().
> This patch fixes all call sites of safe_name().
>
> Mathi
From: Frank Rowand
Fix a memory leak resulting from memory allocation in safe_name().
This patch fixes all call sites of safe_name().
Mathieu Malaterre reported the memory leak on boot:
On my PowerMac device-tree would generate a duplicate name:
[0.023043] device-tree: Duplicate name in Po