[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOesGMjG37FprRX7U-+S3nFCuv=RVAOUv7wb8K-Tcqr26ETevw@mail.gmail.com>
Date: Mon, 13 Jan 2014 10:02:58 -0800
From: Olof Johansson <olof@...om.net>
To: Pavel Machek <pavel@....cz>
Cc: pali.rohar@...il.com, sre@...ian.org, sre@...g0.de,
kernel list <linux-kernel@...r.kernel.org>,
Tony Lindgren <tony@...mide.com>,
linux-omap <linux-omap@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [patch] fix omap compile with randconfig
On Sun, Jan 12, 2014 at 5:00 PM, Pavel Machek <pavel@....cz> wrote:
>
> This fixes:
>
> arch/arm/mach-omap2/built-in.o: In function `omap_reserve':
> /data/l/linux-n900/arch/arm/mach-omap2/common.c:36: undefined
> reference to `omap_fb_reserve_memblock'
>
> Signed-off-by: Pavel Machek <pavel@....cz>
>
> diff --git a/arch/arm/mach-omap2/common.c b/arch/arm/mach-omap2/common.c
> index 9beecde..857907f 100644
> --- a/arch/arm/mach-omap2/common.c
> +++ b/arch/arm/mach-omap2/common.c
> @@ -33,5 +33,7 @@ void __init omap_reserve(void)
> omap_dsp_reserve_sdram_memblock();
> omap_secure_ram_reserve_memblock();
> omap_barrier_reserve_memblock();
> +#ifdef CONFIG_OMAP2_VRFB
> omap_fb_reserve_memblock();
> +#endif
> }
What is this patch against? omap_fb_reserve_memblock() doesn't exist
in v3.13-rc8, nor in -next.
Adding an ifdef here is likely the wrong thing anyway, there should be
a stub provided for !CONFIG_OMAP2_VRFB in the header file instead.
-Olof
--
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