[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <86802c440804022116j2a8fb745pf734f61542a8e287@mail.gmail.com>
Date: Wed, 2 Apr 2008 21:16:05 -0700
From: "Yinghai Lu" <yhlu.kernel@...il.com>
To: "Andrew Morton" <akpm@...ux-foundation.org>
Cc: "Yinghai Lu" <yhlu.kernel.send@...il.com>,
"Ingo Molnar" <mingo@...e.hu>,
"Badari Pulavarty" <pbadari@...ibm.com>, michael@...erman.id.au,
"Kamalesh Babulal" <kamalesh@...ux.vnet.ibm.com>,
linuxppc-dev@...abs.org,
"Balbir Singh" <balbir@...ux.vnet.ibm.com>,
"kernel list" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] mm: make mem_map allocation continuous v2.
On Wed, Apr 2, 2008 at 7:22 PM, Andrew Morton <akpm@...ux-foundation.org> wrote:
> On Wed, 2 Apr 2008 18:30:24 -0700 Yinghai Lu <yhlu.kernel.send@...il.com> wrote:
>
> > v2 replace:
> > [PATCH] mm: make mem_map allocation continuous.
> > [PATCH] mm: allocate section_map for sparse_init
> > [PATCH] mm: allocate usemap at first instead of mem_map in sparse_init
> >
>
> err, no.
>
>
> >
> > diff --git a/mm/sparse.c b/mm/sparse.c
> > index f6a43c0..2881222 100644
> > --- a/mm/sparse.c
> > +++ b/mm/sparse.c
>
> Sorry, but I'd rather not do it this way. We presently have this:
>
it replaces
> mm-make-mem_map-allocation-continuous.patch
> mm-make-mem_map-allocation-continuous-checkpatch-fixes.patch
> mm-allocate-section_map-for-sparse_init.patch
> mm-allocate-section_map-for-sparse_init-update.patch
> mm-allocate-section_map-for-sparse_init-update-fix.patch
> mm-allocate-section_map-for-sparse_init-powerpc-fix.patch
others still needed
so mm-make-mem-map-allocation-continuous.patch will not break powerpc and ia64
YH
--
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