[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <551D0101.6000301@arm.com>
Date: Thu, 02 Apr 2015 09:42:41 +0100
From: Vladimir Murzin <vladimir.murzin@....com>
To: "akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
"mm-commits@...r.kernel.org" <mm-commits@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
"linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>,
"linux-next@...r.kernel.org" <linux-next@...r.kernel.org>,
"sfr@...b.auug.org.au" <sfr@...b.auug.org.au>,
"mhocko@...e.cz" <mhocko@...e.cz>
Subject: Re: mmotm 2015-04-01-14-54 uploaded
On 01/04/15 22:55, akpm@...ux-foundation.org wrote:
> * mm-move-memtest-under-mm.patch
> * mm-move-memtest-under-mm-fix.patch
It was noticed by Paul Bolle (and his clever bot) that patch above
simply disables MEMTEST altogether [1]. Could you fold fix for that, please?
diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
index ea369dd..cd6d74b 100644
--- a/lib/Kconfig.debug
+++ b/lib/Kconfig.debug
@@ -1810,7 +1810,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.
--
[1] https://lkml.org/lkml/2015/3/20/119
Thanks
Vladimir
> * 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 linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists