On Wed, Jun 27, 2018 at 07:58:19AM -0600, Rob Herring wrote: > On Wed, Jun 27, 2018 at 4:11 AM Mike Rapoport <rppt@xxxxxxxxxxxxxxxxxx> wrote: > > > > On Mon, Jun 25, 2018 at 10:09:41AM -0600, Rob Herring wrote: > > > On Mon, Jun 25, 2018 at 8:08 AM Michal Hocko <mhocko@xxxxxxxxxx> wrote: > > > > > > > > Hi, > > > > I am wondering why do we still keep mm/bootmem.c when most architectures > > > > already moved to nobootmem. Is there any fundamental reason why others > > > > cannot or this is just a matter of work? > > > > > > Just because no one has done the work. I did a couple of arches > > > recently (sh, microblaze, and h8300) mainly because I broke them with > > > some DT changes. > > > > I have a patch for alpha nearly ready. > > That leaves m68k and ia64 > > And c6x, hexagon, mips, nios2, unicore32. Those are all the platforms > which don't select NO_BOOTMEM. Yeah, you are right. I've somehow excluded those that HAVE_MEMBLOCK... > Rob > -- Sincerely yours, Mike.
