The patch titled
Subject: mm/memblock.c: fix comment in __next_mem_range()
has been removed from the -mm tree. Its filename was
mm-memblockc-fix-comment-in-the-__next_mem_range.patch
This patch was dropped because it was merged into mainline or a subsystem tree
------------------------------------------------------
From: Alexander Kuleshov <kuleshovmail@xxxxxxxxx>
Subject: mm/memblock.c: fix comment in __next_mem_range()
Signed-off-by: Alexander Kuleshov <kuleshovmail@xxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
mm/memblock.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff -puN mm/memblock.c~mm-memblockc-fix-comment-in-the-__next_mem_range mm/memblock.c
--- a/mm/memblock.c~mm-memblockc-fix-comment-in-the-__next_mem_range
+++ a/mm/memblock.c
@@ -976,7 +976,7 @@ void __init_memblock __next_mem_range(u6
* in type_b.
*
* @idx: pointer to u64 loop variable
- * @nid: nid: node selector, %NUMA_NO_NODE for all nodes
+ * @nid: node selector, %NUMA_NO_NODE for all nodes
* @flags: pick from blocks based on memory attributes
* @type_a: pointer to memblock_type from where the range is taken
* @type_b: pointer to memblock_type which excludes memory from being taken
_
Patches currently in -mm which might be from kuleshovmail@xxxxxxxxx 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
