The patch titled
Subject: mm/memblock: add missing include <linux/bootmem.h>
has been removed from the -mm tree. Its filename was
mm-memblock-add-missing-include-linux-bootmemh.patch
This patch was dropped because it was merged into mainline or a subsystem tree
------------------------------------------------------
From: Mathieu Malaterre <malat@xxxxxxxxxx>
Subject: mm/memblock: add missing include <linux/bootmem.h>
Commit 26f09e9b3a06 ("mm/memblock: add memblock memory allocation apis")
introduced two new function definitions:
`memblock_virt_alloc_try_nid_nopanic'
and
`memblock_virt_alloc_try_nid'.
Commit ea1f5f3712af ("mm: define memblock_virt_alloc_try_nid_raw")
introduced the following function definition:
`memblock_virt_alloc_try_nid_raw'
This commit adds an includeof header file <linux/bootmem.h> to provide the
missing function prototypes. Silence the following gcc warning (W=1):
mm/memblock.c:1334:15: warning: no previous prototype for `memblock_virt_alloc_try_nid_raw' [-Wmissing-prototypes]
mm/memblock.c:1371:15: warning: no previous prototype for `memblock_virt_alloc_try_nid_nopanic' [-Wmissing-prototypes]
mm/memblock.c:1407:15: warning: no previous prototype for `memblock_virt_alloc_try_nid' [-Wmissing-prototypes]
Link: http://lkml.kernel.org/r/20180606194144.16990-1-malat@xxxxxxxxxx
Signed-off-by: Mathieu Malaterre <malat@xxxxxxxxxx>
Reviewed-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
mm/memblock.c | 1 +
1 file changed, 1 insertion(+)
diff -puN mm/memblock.c~mm-memblock-add-missing-include-linux-bootmemh mm/memblock.c
--- a/mm/memblock.c~mm-memblock-add-missing-include-linux-bootmemh
+++ a/mm/memblock.c
@@ -20,6 +20,7 @@
#include <linux/kmemleak.h>
#include <linux/seq_file.h>
#include <linux/memblock.h>
+#include <linux/bootmem.h>
#include <asm/sections.h>
#include <linux/io.h>
_
Patches currently in -mm which might be from malat@xxxxxxxxxx are
--
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
