[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <617e0d57-342d-4162-bd21-ece18e481d87@free.fr>
Date: Mon, 11 Feb 2019 17:47:34 +0100
From: Marc Gonzalez <marc.w.gonzalez@...e.fr>
To: Rob Herring <robh+dt@...nel.org>,
Frank Rowand <frowand.list@...il.com>,
Mike Rapoport <rppt@...ux.ibm.com>,
Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Marek Szyprowski <m.szyprowski@...sung.com>,
Catalin Marinas <catalin.marinas@....com>,
Prateek Patel <prpatel@...dia.com>,
DT <devicetree@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>,
stable <stable@...r.kernel.org>
Subject: Re: [RESEND PATCH v2] of: fix kmemleak crash caused by imbalance in
early memory reservation
On 04/02/2019 15:37, Marc Gonzalez wrote:
> Cc: stable@...r.kernel.org # 3.15+
> Fixes: 3f0c820664483 ("drivers: of: add initialization code for dynamic reserved memory")
> Acked-by: Marek Szyprowski <m.szyprowski@...sung.com>
> Acked-by: Prateek Patel <prpatel@...dia.com>
> Tested-by: Marc Gonzalez <marc.w.gonzalez@...e.fr>
> Signed-off-by: Mike Rapoport <rppt@...ux.ibm.com>
> ---
> Resend with DT CCed to reach robh's patch queue
> I added CC: stable, Fixes, and Prateek's ack
> Trim recipients list to minimize inconvenience
Mike, Stephen,
I'm confused over commit 3532b3b554a216f30edb841d29eef48521bdc592 in linux-next
"memblock: drop __memblock_alloc_base()"
It's definitely going to conflict with the proposed patch
over drivers/of/of_reserved_mem.c
Rob, what's the next step then?
Regards.
Powered by blists - more mailing lists