+ mm-sparse-optimize-memmap-allocation-during-sparse_init-checkpatch-fixes.patch added to -mm tree

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



The patch titled
     Subject: mm-sparse-optimize-memmap-allocation-during-sparse_init-checkpatch-fixes
has been added to the -mm tree.  Its filename is
     mm-sparse-optimize-memmap-allocation-during-sparse_init-checkpatch-fixes.patch

This patch should soon appear at
    http://ozlabs.org/~akpm/mmots/broken-out/mm-sparse-optimize-memmap-allocation-during-sparse_init-checkpatch-fixes.patch
and later at
    http://ozlabs.org/~akpm/mmotm/broken-out/mm-sparse-optimize-memmap-allocation-during-sparse_init-checkpatch-fixes.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: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
Subject: mm-sparse-optimize-memmap-allocation-during-sparse_init-checkpatch-fixes

WARNING: 'numner' may be misspelled - perhaps 'number'?
#159: FILE: mm/sparse.c:591:
+	/* The numner of present sections stored in nr_present_sections

WARNING: Block comments use a trailing */ on a separate line
#167: FILE: mm/sparse.c:599:
+	 * correctly. */

WARNING: line over 80 characters
#219: FILE: mm/sparse-vmemmap.c:299:
+		map_map[nr_consumed_maps] = sparse_mem_map_populate(pnum, nodeid, NULL);

total: 0 errors, 3 warnings, 149 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-sparse-optimize-memmap-allocation-during-sparse_init.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: Baoquan He <bhe@xxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---

 mm/sparse-vmemmap.c |    3 ++-
 mm/sparse.c         |    6 ++++--
 2 files changed, 6 insertions(+), 3 deletions(-)

diff -puN mm/sparse.c~mm-sparse-optimize-memmap-allocation-during-sparse_init-checkpatch-fixes mm/sparse.c
--- a/mm/sparse.c~mm-sparse-optimize-memmap-allocation-during-sparse_init-checkpatch-fixes
+++ a/mm/sparse.c
@@ -588,7 +588,8 @@ void __init sparse_init(void)
 				sizeof(map_map[0]));
 #endif
 
-	/* The numner of present sections stored in nr_present_sections
+	/*
+	 * The number of present sections stored in nr_present_sections
 	 * are kept the same since mem sections are marked as present in
 	 * memory_present(). In this for loop, we need check which sections
 	 * failed to allocate memmap or usemap, then clear its
@@ -596,7 +597,8 @@ void __init sparse_init(void)
 	 * increase 'nr_consumed_maps' whether its allocation of memmap
 	 * or usemap failed or not, so that after we handle the i-th
 	 * memory section, can get memmap and usemap of (i+1)-th section
-	 * correctly. */
+	 * correctly.
+	 */
 	for_each_present_section_nr(0, pnum) {
 		struct mem_section *ms;
 
diff -puN mm/sparse-vmemmap.c~mm-sparse-optimize-memmap-allocation-during-sparse_init-checkpatch-fixes mm/sparse-vmemmap.c
--- a/mm/sparse-vmemmap.c~mm-sparse-optimize-memmap-allocation-during-sparse_init-checkpatch-fixes
+++ a/mm/sparse-vmemmap.c
@@ -296,7 +296,8 @@ void __init sparse_mem_maps_populate_nod
 		if (!present_section_nr(pnum))
 			continue;
 
-		map_map[nr_consumed_maps] = sparse_mem_map_populate(pnum, nodeid, NULL);
+		map_map[nr_consumed_maps] =
+				sparse_mem_map_populate(pnum, nodeid, NULL);
 		if (map_map[nr_consumed_maps++])
 			continue;
 		pr_err("%s: sparsemem memory map backing failed some memory will not be available\n",
_

Patches currently in -mm which might be from akpm@xxxxxxxxxxxxxxxxxxxx are

i-need-old-gcc.patch
arm-arch-arm-include-asm-pageh-needs-personalityh.patch
ocfs2-return-erofs-when-filesystem-becomes-read-only-checkpatch-fixes.patch
mm.patch
tools-modifying-page-types-to-include-shared-map-counts-checkpatch-fixes.patch
tools-modifying-page-types-to-include-shared-map-counts-fix-checkpatch-fixes.patch
tools-adding-support-for-idle-page-tracking-to-tool-fix.patch
mm-drop-vm_bug_on-from-__get_free_pages-fix.patch
mm-list_lruc-fold-__list_lru_count_one-into-its-caller.patch
mm-fadvise-fix-signed-overflow-ubsan-complaint-fix.patch
mm-sparsemem-defer-the-ms-section_mem_map-clearing-fix.patch
mm-sparse-optimize-memmap-allocation-during-sparse_init-checkpatch-fixes.patch
list_lru-prefetch-neighboring-list-entries-before-acquiring-lock-fix.patch
mm-oom-cgroup-aware-oom-killer-fix.patch
mm-oom-cgroup-aware-oom-killer-fix-2.patch
mm-oom-docs-describe-the-cgroup-aware-oom-killer-fix-2-fix.patch
kernel-hung_taskc-allow-to-set-checking-interval-separately-from-timeout-fix.patch
linux-next-rejects.patch
kernel-forkc-export-kernel_thread-to-modules.patch
slab-leaks3-default-y.patch

--
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Kernel Archive]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]

  Powered by Linux