Re: [PATCHSET tip:x86/memblock] memblock: Kill early_node_map[],take 2

From: Ingo Molnar
Date: Mon Dec 05 2011 - 12:28:15 EST



* Tejun Heo <tj@xxxxxxxxxx> wrote:

> (cc'ing Stephen, hi!)
>
> On Mon, Dec 05, 2011 at 05:31:48PM +0100, Ingo Molnar wrote:
> > * Tejun Heo <tj@xxxxxxxxxx> wrote:
> >
> > > Hello,
> > >
> > > This patchset was posted quite a while ago but got lost during the
> > > korg disturbance and I forgot about it too. Thankfully, benh pinged
> > > me about testing this patchset yesterday, so here's the refreshed
> > > version.
> >
> > A bit scary - you should get it into linux-next i suspect - if
> > that works out then we could then put it into tip:core/memblock
> > if there are no objections from anyone.
> >
> > It's not really an x86 tree and most of the changes are
> > affecting non-x86 architectures, right?
>
> Hmmm... this was part of the memblock updates going through
> x86/memblock and unless we're gonna setup a separate tree for memblock
> (I don't think that would be necessary at this point) I think it would
> be better to route this x86/memblock eventually. That said, setting
> up temp linux-next branch for now sounds fine to me. hpa, what do you
> think?

I'm fine with routing this through -tip - the branch can be
tip:core/memblock as this is really not just an x86 series - but
if you could pre-test all the arch impact in linux-next that
would be great ...

Thanks,

Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/