mm-fix-initialization-of-struct-page-for-holes-in-memory-layout-check…

…patch-fixes

WARNING: Unknown commit id '73a6e474cb37', maybe rebased or not pulled?
microsoft#36:
Fixes: 73a6e47 ("mm: memmap_init: iterate over memblock regions rather

WARNING: 'becuase' may be misspelled - perhaps 'because'?
#67: FILE: mm/page_alloc.c:6256:
+ * do not correspond to physical page frames becuase the actual memory bank

total: 0 errors, 2 warnings, 184 lines checked

NOTE: For some of the reported defects, checkpatch may be able to
      mechanically convert to the typical style using --fix or --fix-inplace.

./patches/mm-fix-initialization-of-struct-page-for-holes-in-memory-layout.patch has style problems, please review.

NOTE: If any of the errors are false positives, please report
      them to the maintainer, see CHECKPATCH in MAINTAINERS.

Please run checkpatch prior to sending patches

Cc: Mike Rapoport <rppt@linux.ibm.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>

mm/page_alloc.c

@@ -6257,7 +6257,7 @@ static void __meminit zone_init_free_lists(struct zone *zone)
  * Only struct pages that are backed by physical memory available to the
  * kernel are zeroed and initialized by memmap_init_zone().
  * But, there are some struct pages that are either reserved by firmware or
- * do not correspond to physical page frames becuase the actual memory bank
+ * do not correspond to physical page frames because the actual memory bank
  * is not a multiple of SECTION_SIZE.
  * Fields of those struct pages may be accessed (for example page_to_pfn()
  * on some configuration accesses page flags) so we must explicitly