From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
"H. Peter Anvin" <hpa@zytor.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: [PATCH -v2] x86: Remove dma32_reserve_bootmem
Date: Tue, 12 Apr 2011 10:58:27 -0700 [thread overview]
Message-ID: <20110412105827.443bd56e@jbarnes-desktop> (raw)
In-Reply-To: <4DA491C6.90403@kernel.org>
On Tue, 12 Apr 2011 10:54:14 -0700
Yinghai Lu <yinghai@kernel.org> wrote:
> On 04/12/2011 10:47 AM, Jesse Barnes wrote:
> > On Tue, 12 Apr 2011 10:20:48 -0700
> > 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.
> >>
> >> -v2: rebase on pci-next
> >>
> >> Signed-off-by: Yinghai Lu<yinghai@kernel.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.
>
> sorry for that. looks like recent thunderbird upgrade convert TAB to space..
Thanks for checking. I wonder why every mailer (and some MTAs!) feel
the need to molest message content so thoroughly...
--
Jesse Barnes, Intel Open Source Technology Center
next prev parent reply other threads:[~2011-04-12 17:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-28 17:56 [PATCH] " Yinghai Lu
2011-04-12 16:11 ` Jesse Barnes
2011-04-12 17:20 ` [PATCH -v2] " Yinghai Lu
2011-04-12 17:47 ` Jesse Barnes
2011-04-12 17:54 ` Yinghai Lu
2011-04-12 17:58 ` Jesse Barnes [this message]
2011-04-12 19:25 ` Yinghai Lu
2011-04-12 20:18 ` Yinghai Lu
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=20110412105827.443bd56e@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@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