Re: Git next: Second stage of cpu_alloc patches

From: Andrew Morton
Date: Wed Nov 05 2008 - 11:28:34 EST


On Wed, 5 Nov 2008 07:54:39 -0600 (CST) Christoph Lameter <cl@xxxxxxxxxxxxxxxxxxxx> wrote:

> On Tue, 4 Nov 2008, Andrew Morton wrote:
>
> > On Tue, 4 Nov 2008 20:56:52 -0600 (CST) Christoph Lameter <cl@xxxxxxxxxxxxxxxxxxxx> wrote:
> >
> >> The second stage of the cpu_alloc patchset can be pulled from
> >>
> >> kernel.org/pub/scm/linux/kernel/git/christoph/work.git cpu_alloc_stage2
> >
> > Please send the patches for review. Always.
>
> Well okay can we define a process how to get patches merged with the -next
> tree involved? It was nice when you handled all of this but the last
> version of the cpu_alloc was thrown out of mm because of a -next conflict
> and so it seemed better to go to the source than risk this again.
>
> > I've forgotten how this whole cpu_alloc thing worked and now it's all
> > stuffed away in some git tree somewhere. Oh well, whee...
>
> Ok so post a patchset to lkml and at the same time offer a git tree?

Sure.

For important things I think it doesn't hurt to resend even if they've
been "reviewed" beforehand. Particularly if you don't think enough
attention was paid to them.

These patches are a good example of that. By the time 2.6.29 opens
everyone will have forgotten what all this stuff does and how it
works.

We need to get alpha sorted out too. Frankly, if we can't get anyone to
review/test/ack the alpha genirq conversion then I'd say merge it
anyway. I'll make sure that it at least compiles.
--
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/