From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Yinghai Lu <yinghai@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86: Remove dma32_reserve_bootmem
Date: Mon, 28 Mar 2011 09:23:29 -0700 [thread overview]
Message-ID: <20110328092329.6e5ac682@jbarnes-desktop> (raw)
In-Reply-To: <20110328162213.GA20191@elte.hu>
On Mon, 28 Mar 2011 18:22:13 +0200
Ingo Molnar <mingo@elte.hu> wrote:
>
> * Jesse Barnes <jbarnes@virtuousgeek.org> wrote:
>
> > On Thu, 24 Mar 2011 09:03:26 +0100
> > Ingo Molnar <mingo@elte.hu> wrote:
> >
> > >
> > > * Yinghai Lu <yinghai@kernel.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.
> > > >
> > > > Signed-off-by: Yinghai Lu <yinghai@kernel.org>
> > > >
> > > > ---
> > > > arch/x86/include/asm/pci.h | 2 -
> > > > arch/x86/kernel/pci-dma.c | 64 ---------------------------------------------
> > > > arch/x86/kernel/setup.c | 1
> > > > 3 files changed, 67 deletions(-)
> > >
> > > Cc:-ing Jesse - i suspect this should be handled by the PCI tree.
> >
> > Please re-send, sounds good in theory but I'd like to see the patch.
>
> It should be in your lkml folder, the first mail in this thread has the patch.
If I kept everything in my lkml folder maybe... :)
--
Jesse Barnes, Intel Open Source Technology Center
next prev parent reply other threads:[~2011-03-28 16:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-24 5:30 Yinghai Lu
2011-03-24 8:03 ` Ingo Molnar
2011-03-28 16:19 ` Jesse Barnes
2011-03-28 16:22 ` Ingo Molnar
2011-03-28 16:23 ` Jesse Barnes [this message]
2011-03-28 17:56 Yinghai Lu
2011-04-12 16:11 ` Jesse Barnes
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=20110328092329.6e5ac682@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=yinghai@kernel.org \
/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
Powered by JetHome