* Felipe Contreras <felipe.contre...@gmail.com> [101107 13:34]:
> Also, don't be picky about the location, which incidentally fixes the
> build since MEMBLOCK_REAL_LIMIT is gone on 2.6.37.
> 
> Signed-off-by: Felipe Contreras <felipe.contre...@gmail.com>

This is a valid fix for 2.6.37 -rc cycle now that the memblock code
is in and should get merged with other drivers/staging/tidspbridge
related fixes.

Acked-by: Tony Lindgren <t...@atomide.com>

> ---
>  arch/arm/plat-omap/devices.c |    4 +++-
>  1 files changed, 3 insertions(+), 1 deletions(-)
> 
> diff --git a/arch/arm/plat-omap/devices.c b/arch/arm/plat-omap/devices.c
> index 6f42a18..fc81912 100644
> --- a/arch/arm/plat-omap/devices.c
> +++ b/arch/arm/plat-omap/devices.c
> @@ -284,12 +284,14 @@ void __init omap_dsp_reserve_sdram_memblock(void)
>       if (!size)
>               return;
>  
> -     paddr = __memblock_alloc_base(size, SZ_1M, MEMBLOCK_REAL_LIMIT);
> +     paddr = memblock_alloc(size, SZ_1M);
>       if (!paddr) {
>               pr_err("%s: failed to reserve %x bytes\n",
>                               __func__, size);
>               return;
>       }
> +     memblock_free(paddr, size);
> +     memblock_remove(paddr, size);
>  
>       omap_dsp_phys_mempool_base = paddr;
>  }
> -- 
> 1.7.3.2.3.gf8529
> 
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to