From: Vladimir Murzin <vladimir.murzin@arm.com>
To: "akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"mm-commits@vger.kernel.org" <mm-commits@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
"sfr@canb.auug.org.au" <sfr@canb.auug.org.au>,
"mhocko@suse.cz" <mhocko@suse.cz>
Subject: Re: mmotm 2015-04-01-14-54 uploaded
Date: Thu, 02 Apr 2015 09:42:41 +0100 [thread overview]
Message-ID: <551D0101.6000301@arm.com> (raw)
In-Reply-To: <551c6943.H+vcYDrtw2kStb+B%akpm@linux-foundation.org>
On 01/04/15 22:55, akpm@linux-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, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Vladimir Murzin <vladimir.murzin@arm.com>
To: "akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"mm-commits@vger.kernel.org" <mm-commits@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
"sfr@canb.auug.org.au" <sfr@canb.auug.org.au>,
"mhocko@suse.cz" <mhocko@suse.cz>
Subject: Re: mmotm 2015-04-01-14-54 uploaded
Date: Thu, 02 Apr 2015 09:42:41 +0100 [thread overview]
Message-ID: <551D0101.6000301@arm.com> (raw)
In-Reply-To: <551c6943.H+vcYDrtw2kStb+B%akpm@linux-foundation.org>
On 01/04/15 22:55, akpm@linux-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
next prev parent reply other threads:[~2015-04-02 8:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-01 21:55 mmotm 2015-04-01-14-54 uploaded akpm
2015-04-01 21:55 ` akpm
2015-04-02 8:42 ` Vladimir Murzin [this message]
2015-04-02 8:42 ` Vladimir Murzin
2015-04-02 18:52 ` Paul Bolle
2015-04-02 18:52 ` Paul Bolle
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=551D0101.6000301@arm.com \
--to=vladimir.murzin@arm.com \
--cc=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-next@vger.kernel.org \
--cc=mhocko@suse.cz \
--cc=mm-commits@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.