The patch titled
Subject: mm-move-memtest-under-mm-fix-fix
has been added to the -mm tree. Its filename is
mm-move-memtest-under-mm-fix-fix.patch
This patch should soon appear at
http://ozlabs.org/~akpm/mmots/broken-out/mm-move-memtest-under-mm-fix-fix.patch
and later at
http://ozlabs.org/~akpm/mmotm/broken-out/mm-move-memtest-under-mm-fix-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: mm-move-memtest-under-mm-fix-fix
It was noticed by Paul Bolle that patch above simply disables MEMTEST
altogether. ?
Reported-by: Paul Bolle <pebolle@xxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
lib/Kconfig.debug | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff -puN lib/Kconfig.debug~mm-move-memtest-under-mm-fix-fix lib/Kconfig.debug
--- a/lib/Kconfig.debug~mm-move-memtest-under-mm-fix-fix
+++ a/lib/Kconfig.debug
@@ -1734,7 +1734,7 @@ config TEST_UDELAY
config MEMTEST
bool "Memtest"
- depends on MEMBLOCK
+ depends on HAVE_MEMBLOCK
---help---
This option adds a kernel parameter 'memtest', which allows memtest
to be set.
_
Patches currently in -mm which might be from vladimir.murzin@xxxxxxx are
mm-move-memtest-under-mm.patch
mm-move-memtest-under-mm-fix.patch
mm-move-memtest-under-mm-fix-fix.patch
memtest-use-phys_addr_t-for-physical-addresses.patch
arm64-add-support-for-memtest.patch
arm-add-support-for-memtest.patch
kconfig-memtest-update-number-of-test-patterns-up-to-17.patch
documentation-update-arch-list-in-the-memtest-entry.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
