The patch titled
Subject: mm/memblock.c: fix a typo in __next_mem_pfn_range() comments
has been added to the -mm tree. Its filename is
mm-fix-a-typo-in-__next_mem_pfn_range-comments.patch
This patch should soon appear at
http://ozlabs.org/~akpm/mmots/broken-out/mm-fix-a-typo-in-__next_mem_pfn_range-comments.patch
and later at
http://ozlabs.org/~akpm/mmotm/broken-out/mm-fix-a-typo-in-__next_mem_pfn_range-comments.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/process/submit-checklist.rst when testing your code ***
The -mm tree is included into linux-next and is updated
there every 3-4 working days
------------------------------------------------------
From: Chen Chang <rainccrun@xxxxxxxxx>
Subject: mm/memblock.c: fix a typo in __next_mem_pfn_range() comments
Link: http://lkml.kernel.org/r/20181107100247.13359-1-rainccrun@xxxxxxxxx
Signed-off-by: Chen Chang <rainccrun@xxxxxxxxx>
Acked-by: Michal Hocko <mhocko@xxxxxxxx>
Acked-by: Mike Rapoport <rppt@xxxxxxxxxxxxx>
Reviewed-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
mm/memblock.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/mm/memblock.c~mm-fix-a-typo-in-__next_mem_pfn_range-comments
+++ a/mm/memblock.c
@@ -1179,7 +1179,7 @@ void __init_memblock __next_mem_range_re
#ifdef CONFIG_HAVE_MEMBLOCK_NODE_MAP
/*
- * Common iterator interface used to define for_each_mem_range().
+ * Common iterator interface used to define for_each_mem_pfn_range().
*/
void __init_memblock __next_mem_pfn_range(int *idx, int nid,
unsigned long *out_start_pfn,
_
Patches currently in -mm which might be from rainccrun@xxxxxxxxx are
mm-fix-a-typo-in-__next_mem_pfn_range-comments.patch
