Re: [PATCH 03/30] mm: remove CONFIG_HAVE_MEMBLOCK
From: Mike Rapoport <hidden>
Date: 2018-09-26 11:54:29
Also in:
linux-alpha, linux-mips, linux-mm, linux-riscv, linux-s390, linux-sh, linux-um, linuxppc-dev, sparclinux
Possibly related (same subject, not in this thread)
- 2018-09-27 · Re: [PATCH 03/30] mm: remove CONFIG_HAVE_MEMBLOCK · Mike Rapoport <hidden>
- 2018-09-27 · Re: [PATCH 03/30] mm: remove CONFIG_HAVE_MEMBLOCK · Alexander Duyck <hidden>
- 2018-09-26 · Re: [PATCH 03/30] mm: remove CONFIG_HAVE_MEMBLOCK · Mike Rapoport <hidden>
- 2018-09-26 · Re: [PATCH 03/30] mm: remove CONFIG_HAVE_MEMBLOCK · Alexander Duyck <hidden>
On Wed, Sep 26, 2018 at 11:24:04AM +0200, Michal Hocko wrote:
On Fri 14-09-18 15:10:18, Mike Rapoport wrote:quoted
All architecures use memblock for early memory management. There is no need for the CONFIG_HAVE_MEMBLOCK configuration option.git grep says arch/csky/Kconfig: select HAVE_MEMBLOCK
Not only that, there are other bootmem leftovers in csky. I've sent the patch with the necessary fixups [1] [1] https://lkml.kernel.org/lkml/20180926112744.GC4628@rapoport-lnx/
quoted
Signed-off-by: Mike Rapoport <redacted>Other than that Acked-by: Michal Hocko <mhocko@suse.com> -- Michal Hocko SUSE Labs
-- Sincerely yours, Mike.