linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Wei Yang <richard.weiyang@gmail.com>
To: Mike Rapoport <rppt@kernel.org>
Cc: Wei Yang <richard.weiyang@gmail.com>,
	akpm@linux-foundation.org, linux-mm@kvack.org
Subject: Re: [Patch v2 1/2] mm/mm_init.c: use memblock_region_memory_base_pfn() to get startpfn
Date: Sat, 25 May 2024 02:23:46 +0000	[thread overview]
Message-ID: <20240525022346.3fqzm45ndahtncsn@master> (raw)
In-Reply-To: <ZlBM5fXXrsZHwFXi@kernel.org>

On Fri, May 24, 2024 at 11:16:37AM +0300, Mike Rapoport wrote:
>On Fri, May 24, 2024 at 01:19:13AM +0000, Wei Yang wrote:
>> Just like what it does in "if (mirrored_kernelcore)", we should use
>> memblock_region_memory_base_pfn() to get the startpfn.
>> 
>> Signed-off-by: Wei Yang <richard.weiyang@gmail.com>
>> ---
>>  include/linux/memblock.h | 2 +-
>>  mm/mm_init.c             | 2 +-
>>  2 files changed, 2 insertions(+), 2 deletions(-)
>> 
>> diff --git a/include/linux/memblock.h b/include/linux/memblock.h
>> index e2082240586d..6cf18dc2b4d0 100644
>> --- a/include/linux/memblock.h
>> +++ b/include/linux/memblock.h
>> @@ -565,7 +565,7 @@ static inline unsigned long memblock_region_reserved_end_pfn(const struct memblo
>>  }
>>  
>>  /**
>> - * for_each_mem_region - itereate over memory regions
>> + * for_each_mem_region - iterate over memory regions
>
>Sorry I've missed this in v1, but it should be a separate patch

Sure, will separate it.


-- 
Wei Yang
Help you, Help me


      reply	other threads:[~2024-05-25  2:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-24  1:19 Wei Yang
2024-05-24  1:19 ` [Patch v2 2/2] mm/mm_init.c: move nr_initialised reset down a bit Wei Yang
2024-05-24  8:16 ` [Patch v2 1/2] mm/mm_init.c: use memblock_region_memory_base_pfn() to get startpfn Mike Rapoport
2024-05-25  2:23   ` Wei Yang [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240525022346.3fqzm45ndahtncsn@master \
    --to=richard.weiyang@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-mm@kvack.org \
    --cc=rppt@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox