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

Re: [PATCH v2 12/17] arch, drivers: replace for_each_membock() with for_each_mem_range()

From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Date: 2020-08-05 16:06:54
Also in: linux-arch, linux-arm-kernel, linux-iommu, linux-mips, linux-mm, linux-riscv, linux-s390, linux-sh, lkml, sparclinux

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

There are several occurrences of the following pattern:

	for_each_memblock(memory, reg) {
		start = __pfn_to_phys(memblock_region_memory_base_pfn(reg);
		end = __pfn_to_phys(memblock_region_memory_end_pfn(reg));

		/* do something with start and end */
	}

Using for_each_mem_range() iterator is more appropriate in such cases and
allows simpler and cleaner code.

Signed-off-by: Mike Rapoport <redacted>
---
 arch/mips/cavium-octeon/dma-octeon.c     | 12 +++---
 arch/mips/kernel/setup.c                 | 31 +++++++--------
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 ]
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help