From: Vladimir Murzin <vladimir.murzin@arm.com>
To: Paul Bolle <pebolle@tiscali.nl>, Guenter Roeck <linux@roeck-us.net>
Cc: "valentinrothberg@gmail.com" <valentinrothberg@gmail.com>,
"rupran@einserver.de" <rupran@einserver.de>,
"stefan.hengelein@fau.de" <stefan.hengelein@fau.de>,
Andrew Morton <akpm@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -next] mm: MEMTEST depends on MEMBLOCK
Date: Fri, 20 Mar 2015 10:39:30 +0000 [thread overview]
Message-ID: <550BF8E2.9020002@arm.com> (raw)
In-Reply-To: <1426847014.23529.35.camel@x220>
On 20/03/15 10:23, Paul Bolle wrote:
> On Fri, 2015-03-13 at 02:03 -0700, Guenter Roeck wrote:
>> Building alpha:allmodconfig fails with
>>
>> mm/memtest.c: In function 'reserve_bad_mem':
>> mm/memtest.c:38:2: error: implicit declaration of function 'memblock_reserve'
>> mm/memtest.c: In function 'do_one_pass':
>> mm/memtest.c:77:2: error: implicit declaration of function 'for_each_free_mem_range'
>> mm/memtest.c:77:73: error: expected ';' before '{' token
>>
>> because it depends on MEMBLOCK which is not defined for the alpha
>> architecture.
>>
>> Fixes: 420c89e6185d ("mm: move memtest under mm")
>> Cc: Vladimir Murzin <vladimir.murzin@arm.com>
>> Signed-off-by: Guenter Roeck <linux@roeck-us.net>
>> ---
>> lib/Kconfig.debug | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
>> index 8b4e69a..dc1e69c 100644
>> --- a/lib/Kconfig.debug
>> +++ b/lib/Kconfig.debug
>> @@ -1797,6 +1797,7 @@ config TEST_UDELAY
>>
>> config MEMTEST
>> bool "Memtest"
>> + depends on MEMBLOCK
>> ---help---
>> This option adds a kernel parameter 'memtest', which allows memtest
>> to be set.
>
> (There's now a bot checking this stuff, but I couldn't resist reporting
> it when my script spotted it.)
>
> Please do
> $ git grep -n "config\s\+MEMBLOCK\b" next-20150320
> $ git grep -n "config\s\+MEMBLOCK\b" v4.0-rc4
>
> I think this patch simply disables MEMTEST altogether. I'm guessing this
I should have tested it before... yes, you (and bot) are right, after
patch applied memtest is not available at arm/arm64 which definitely has
memblock.
> should have added
> depends on HAVE_MEMBLOCK
>
Could we fold this change or separate patch is needed?
Cheers
Vladimir
>
> Paul Bolle
>
>
next prev parent reply other threads:[~2015-03-20 10:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-13 9:03 [PATCH -next] mm: MEMTEST depends on MEMBLOCK Guenter Roeck
2015-03-13 9:55 ` Vladimir Murzin
2015-03-16 11:04 ` Geert Uytterhoeven
2015-03-20 10:23 ` Paul Bolle
2015-03-20 10:39 ` Vladimir Murzin [this message]
2015-03-20 10:52 ` Paul Bolle
2015-03-20 10:59 ` Valentin Rothberg
2015-03-20 14:34 ` Stefan Hengelein
2015-03-20 15:11 ` 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=550BF8E2.9020002@arm.com \
--to=vladimir.murzin@arm.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=pebolle@tiscali.nl \
--cc=rupran@einserver.de \
--cc=stefan.hengelein@fau.de \
--cc=valentinrothberg@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox