On Tue, Jul 28, 2020 at 08:11:43AM +0300, Mike Rapoport wrote:
> From: Mike Rapoport <r...@linux.ibm.com>
> 
> Instead of traversing memblock.memory regions to find memory_start and
> memory_end, simply query memblock_{start,end}_of_DRAM().
> 
> Signed-off-by: Mike Rapoport <r...@linux.ibm.com>
> ---
>  arch/h8300/kernel/setup.c    | 8 +++-----
>  arch/nds32/kernel/setup.c    | 8 ++------
>  arch/openrisc/kernel/setup.c | 9 ++-------
>  3 files changed, 7 insertions(+), 18 deletions(-)

Hi Mike,

For the openrisc part:

Acked-by: Stafford Horne <sho...@gmail.com>

> --- a/arch/openrisc/kernel/setup.c
> +++ b/arch/openrisc/kernel/setup.c
> @@ -48,17 +48,12 @@ static void __init setup_memory(void)
>       unsigned long ram_start_pfn;
>       unsigned long ram_end_pfn;
>       phys_addr_t memory_start, memory_end;
> -     struct memblock_region *region;
>  
>       memory_end = memory_start = 0;
>  
>       /* Find main memory where is the kernel, we assume its the only one */
> -     for_each_memblock(memory, region) {
> -             memory_start = region->base;
> -             memory_end = region->base + region->size;
> -             printk(KERN_INFO "%s: Memory: 0x%x-0x%x\n", __func__,
> -                    memory_start, memory_end);
> -     }
> +     memory_start = memblock_start_of_DRAM();
> +     memory_end = memblock_end_of_DRAM();
>  
>       if (!memory_end) {
>               panic("No memory!");
> -- 
> 2.26.2
> 

Reply via email to