[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110412104716.5388849d@jbarnes-desktop>
Date: Tue, 12 Apr 2011 10:47:16 -0700
From: Jesse Barnes <jbarnes@...tuousgeek.org>
To: Yinghai Lu <yinghai@...nel.org>
Cc: Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...e.hu>,
"H. Peter Anvin" <hpa@...or.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>
Subject: Re: [PATCH -v2] x86: Remove dma32_reserve_bootmem
On Tue, 12 Apr 2011 10:20:48 -0700
Yinghai Lu <yinghai@...nel.org> wrote:
>
> That is workaround for holding dma32 buf when early bootmem could use up
> those range on system that have lots of RAM.
>
> Now x86 is using memblock, and even nobootmem wrapper do top-down allocation.
>
> So We could remove those not needed code now.
>
> -v2: rebase on pci-next
>
> Signed-off-by: Yinghai Lu <yinghai@...nel.org>
>
Hm, still didn't apply cleanly, I guess the patch got corrupted. I
fixed it up by hand and applied to linux-next though, thanks.
--
Jesse Barnes, Intel Open Source Technology Center
--
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