[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87lgd2tgsc.wl-ysato@users.sourceforge.jp>
Date: Wed, 02 May 2018 20:53:39 +0900
From: Yoshinori Sato <ysato@...rs.sourceforge.jp>
To: Rob Herring <robh@...nel.org>
Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"moderated list:H8/300 ARCHITECTURE"
<uclinux-h8-devel@...ts.sourceforge.jp>
Subject: Re: [PATCH] h8300: switch to NO_BOOTMEM
On Wed, 02 May 2018 11:33:41 +0900,
Rob Herring wrote:
>
> On Fri, Mar 16, 2018 at 4:33 PM, Rob Herring <robh@...nel.org> wrote:
> > Commit 0fa1c579349f ("of/fdt: use memblock_virt_alloc for early alloc")
> > inadvertently switched the DT unflattening allocations from memblock to
> > bootmem which doesn't work because the unflattening happens before
> > bootmem is initialized. Swapping the order of bootmem init and
> > unflattening could also fix this, but removing bootmem is desired. So
> > enable NO_BOOTMEM on h8300 like other architectures have done.
> >
> > Fixes: 0fa1c579349f ("of/fdt: use memblock_virt_alloc for early alloc")
> > Cc: Yoshinori Sato <ysato@...rs.sourceforge.jp>
> > Cc: uclinux-h8-devel@...ts.sourceforge.jp
> > Signed-off-by: Rob Herring <robh@...nel.org>
> > ---
> > I haven't seen any reports, but 4.16 is likely broken. This is compile
> > tested only.
> >
> > Moving unflattening after bootmem_init should also work if a smaller
> > change for 4.16 is desired.
>
> Ping! Someone going to pick this up?
>
> Rob
Sorry. I looked out.
Please wait several days to confirm.
--
Yosinori Sato
Powered by blists - more mailing lists