From: Huaisheng Ye <yehs1@lenovo.com>
To: akpm@linux-foundation.org
Cc: linux-mm@kvack.org, Huaisheng Ye <yehs1@lenovo.com>
Subject: [PATCH] mm/memblock: fix a typo in comment
Date: Wed, 4 Apr 2018 20:40:58 +0800 [thread overview]
Message-ID: <1522845658-21439-1-git-send-email-yehs1@lenovo.com> (raw)
__next_reserved_mem_region is used by for_each_reserved_mem_region.
Signed-off-by: Huaisheng Ye <yehs1@lenovo.com>
---
mm/memblock.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/mm/memblock.c b/mm/memblock.c
index 48376bd..5f36cab 100644
--- a/mm/memblock.c
+++ b/mm/memblock.c
@@ -810,7 +810,7 @@ int __init_memblock memblock_clear_nomap(phys_addr_t base, phys_addr_t size)
}
/**
- * __next_reserved_mem_region - next function for for_each_reserved_region()
+ * __next_reserved_mem_region - next function for for_each_reserved_mem_region()
* @idx: pointer to u64 loop variable
* @out_start: ptr to phys_addr_t for start address of the region, can be %NULL
* @out_end: ptr to phys_addr_t for end address of the region, can be %NULL
--
1.8.3.1
reply other threads:[~2018-04-04 12:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1522845658-21439-1-git-send-email-yehs1@lenovo.com \
--to=yehs1@lenovo.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.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;
as well as URLs for NNTP newsgroup(s).