The patch titled
Subject: mm/memblock: make memblock_remove_range() static
has been removed from the -mm tree. Its filename was
mm-memblock-make-memblock_remove_range-static.patch
This patch was dropped because it was merged into mainline or a subsystem tree
------------------------------------------------------
From: Alexander Kuleshov <kuleshovmail@xxxxxxxxx>
Subject: mm/memblock: make memblock_remove_range() static
memblock_remove_range() is only used in the mm/memblock.c, so we can make
it static.
Signed-off-by: Alexander Kuleshov <kuleshovmail@xxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
include/linux/memblock.h | 4 ----
mm/memblock.c | 2 +-
2 files changed, 1 insertion(+), 5 deletions(-)
diff -puN include/linux/memblock.h~mm-memblock-make-memblock_remove_range-static include/linux/memblock.h
--- a/include/linux/memblock.h~mm-memblock-make-memblock_remove_range-static
+++ a/include/linux/memblock.h
@@ -89,10 +89,6 @@ int memblock_add_range(struct memblock_t
phys_addr_t base, phys_addr_t size,
int nid, unsigned long flags);
-int memblock_remove_range(struct memblock_type *type,
- phys_addr_t base,
- phys_addr_t size);
-
void __next_mem_range(u64 *idx, int nid, ulong flags,
struct memblock_type *type_a,
struct memblock_type *type_b, phys_addr_t *out_start,
diff -puN mm/memblock.c~mm-memblock-make-memblock_remove_range-static mm/memblock.c
--- a/mm/memblock.c~mm-memblock-make-memblock_remove_range-static
+++ a/mm/memblock.c
@@ -706,7 +706,7 @@ static int __init_memblock memblock_isol
return 0;
}
-int __init_memblock memblock_remove_range(struct memblock_type *type,
+static int __init_memblock memblock_remove_range(struct memblock_type *type,
phys_addr_t base, phys_addr_t size)
{
int start_rgn, end_rgn;
_
Patches currently in -mm which might be from kuleshovmail@xxxxxxxxx are
mm-hugetlb-make-node_hstates-array-static.patch
lib-halfmd4-use-rol32-inline-function-in-the-round-macro.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
