[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20231206213110.GA3345785-robh@kernel.org>
Date: Wed, 6 Dec 2023 15:31:10 -0600
From: Rob Herring <robh@...nel.org>
To: Oreoluwa Babatunde <quic_obabatun@...cinc.com>
Cc: catalin.marinas@....com, will@...nel.org, frowand.list@...il.com,
dinguyen@...nel.org, chenhuacai@...nel.org,
tsbogend@...ha.franken.de, jonas@...thpole.se,
stefan.kristiansson@...nalahti.fi, shorne@...il.com,
mpe@...erman.id.au, ysato@...rs.sourceforge.jp, dalias@...c.org,
glaubitz@...sik.fu-berlin.de, richard@....at,
anton.ivanov@...bridgegreys.com, johannes@...solutions.net,
chris@...kel.net, jcmvbkbc@...il.com,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
devicetree@...r.kernel.org, linux-arm-msm@...r.kernel.org,
kernel@...cinc.com
Subject: Re: [RFC PATCH v2 2/6] of: reserved_mem: Swicth call to
unflatten_device_tree() to after paging_init()
On Mon, Dec 04, 2023 at 10:54:05AM -0800, Oreoluwa Babatunde wrote:
> Switch call to unflatten_device_tree() to after paging_init() on other
> archs to follow new order in which the reserved_mem regions are
> processed.
You did this so that you could allocate memory for the reserved regions.
But unflatten_device_tree() can already do allocations using memblock.
So the same thing should work for you.
I suspect that moving this will break any arch that called an of_* API
between the original call and the new call location.
Rob
Powered by blists - more mailing lists