[PATCH v3] MIPS: replace add_memory_region with memblock
Thomas Bogendoerfer
tsbogend at alpha.franken.de
Mon Oct 12 06:31:23 EDT 2020
On Fri, Oct 09, 2020 at 02:14:46PM +0200, Thomas Bogendoerfer wrote:
> add_memory_region was the old interface for registering memory and
> was already changed to used memblock internaly. Replace it by
> directly calling memblock functions.
>
> Signed-off-by: Thomas Bogendoerfer <tsbogend at alpha.franken.de>
> ---
> Changes in v3:
> removed early_init_dt_add_memory_arch and
> early_init_dt_reserve_memory_arch as there is nothing
> special about our version and we can use the generic ones
>
> Changes in v2:
> fixed missing memblock include in fw/sni/sniprom.c
> tested on cobalt, IP22, IP28, IP30, IP32, JAZZ, SNI
>
> arch/mips/alchemy/common/prom.c | 3 +-
> arch/mips/ar7/memory.c | 2 +-
> arch/mips/ath25/ar2315.c | 3 +-
> arch/mips/ath25/ar5312.c | 3 +-
> arch/mips/bcm47xx/prom.c | 3 +-
> arch/mips/bcm47xx/setup.c | 2 +-
> arch/mips/bcm63xx/setup.c | 2 +-
> arch/mips/cavium-octeon/setup.c | 24 ++++++-------
> arch/mips/cobalt/setup.c | 3 +-
> arch/mips/dec/prom/memory.c | 8 ++---
> arch/mips/fw/arc/memory.c | 28 ++++++++++-----
> arch/mips/fw/sni/sniprom.c | 4 +--
> arch/mips/include/asm/bootinfo.h | 7 ----
> arch/mips/include/asm/netlogic/psb-bootinfo.h | 1 +
> arch/mips/kernel/prom.c | 25 --------------
> arch/mips/kernel/setup.c | 50 ++++-----------------------
> arch/mips/loongson2ef/common/mem.c | 12 ++-----
> arch/mips/loongson32/common/prom.c | 4 +--
> arch/mips/netlogic/xlp/setup.c | 2 +-
> arch/mips/netlogic/xlr/setup.c | 5 +--
> arch/mips/ralink/of.c | 3 +-
> arch/mips/rb532/prom.c | 2 +-
> arch/mips/sgi-ip32/ip32-memory.c | 3 +-
> arch/mips/sibyte/common/cfe.c | 16 ++++-----
> arch/mips/txx9/jmr3927/prom.c | 4 +--
> arch/mips/txx9/rbtx4927/prom.c | 5 +--
> arch/mips/txx9/rbtx4938/prom.c | 3 +-
> arch/mips/txx9/rbtx4939/prom.c | 4 +--
> 28 files changed, 82 insertions(+), 149 deletions(-)
applied to mips-next.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
More information about the linux-arm-kernel
mailing list