The patch titled
Subject: memtest-cleanup-log-messages-fix
has been added to the -mm tree. Its filename is
memtest-cleanup-log-messages-fix.patch
This patch should soon appear at
http://ozlabs.org/~akpm/mmots/broken-out/memtest-cleanup-log-messages-fix.patch
and later at
http://ozlabs.org/~akpm/mmotm/broken-out/memtest-cleanup-log-messages-fix.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/SubmitChecklist when testing your code ***
The -mm tree is included into linux-next and is updated
there every 3-4 working days
------------------------------------------------------
From: Vladimir Murzin <vladimir.murzin@xxxxxxx>
Subject: memtest-cleanup-log-messages-fix
Cc: Leon Romanovsky <leon@xxxxxxx>
Cc: David Rientjes <rientjes@xxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
mm/memtest.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff -puN mm/memtest.c~memtest-cleanup-log-messages-fix mm/memtest.c
--- a/mm/memtest.c~memtest-cleanup-log-messages-fix
+++ a/mm/memtest.c
@@ -31,7 +31,7 @@ static u64 patterns[] __initdata = {
static void __init reserve_bad_mem(u64 pattern, phys_addr_t start_bad, phys_addr_t end_bad)
{
- pr_info("%016llx bad mem addr %pa - %pa reserved\n",
+ pr_info(" %016llx bad mem addr %pa - %pa reserved\n",
cpu_to_be64(pattern), &start_bad, &end_bad);
memblock_reserve(start_bad, end_bad - start_bad);
}
_
Patches currently in -mm which might be from vladimir.murzin@xxxxxxx are
memtest-use-kstrtouint-instead-of-simple_strtoul.patch
memtest-cleanup-log-messages.patch
memtest-cleanup-log-messages-fix.patch
memtest-remove-unused-header-files.patch
memblock-make-memblock_overlaps_region-return-bool.patch
mem-hotplug-handle-node-hole-when-initializing-numa_meminfo.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
