Thread (34 messages) 34 messages, 6 authors, 2020-08-05

Re: [PATCH v2 17/17] memblock: use separate iterators for memory and reserved regions

From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Date: 2020-08-05 13:08:42
Also in: linux-arch, linux-iommu, linux-mips, linux-mm, linux-riscv, linux-s390, linux-sh, linuxppc-dev, lkml, sparclinux

On Sun, Aug 02, 2020 at 07:36:01PM +0300, Mike Rapoport wrote:
From: Mike Rapoport <redacted>

for_each_memblock() is used to iterate over memblock.memory in
a few places that use data from memblock_region rather than the memory
ranges.

Introduce separate for_each_mem_region() and for_each_reserved_mem_region()
to improve encapsulation of memblock internals from its users.

Signed-off-by: Mike Rapoport <redacted>
---
 arch/mips/netlogic/xlp/setup.c |  2 +-
Acked-by: Thomas Bogendoerfer <tsbogend@alpha.franken.de>

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help