[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5502B3F6.2050603@arm.com>
Date: Fri, 13 Mar 2015 09:55:02 +0000
From: Vladimir Murzin <vladimir.murzin@....com>
To: Guenter Roeck <linux@...ck-us.net>,
Andrew Morton <akpm@...ux-foundation.org>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH -next] mm: MEMTEST depends on MEMBLOCK
On 13/03/15 09:03, 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@....com>
> Signed-off-by: Guenter Roeck <linux@...ck-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.
>
Thanks for fixing it!
Acked-by: Vladimir Murzin <vladimir.murzin@....com>
Cheers
Vladimir
--
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