All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Christoph Lameter <cl@linux-foundation.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-kernel@vger.kernel.org, travis@sgi.com
Subject: Re: Git next: Second stage of cpu_alloc patches
Date: Wed, 5 Nov 2008 08:27:54 -0800	[thread overview]
Message-ID: <20081105082754.2d41f0d1.akpm@linux-foundation.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0811050753120.11867@quilx.com>

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

> On Tue, 4 Nov 2008, Andrew Morton wrote:
> 
> > On Tue, 4 Nov 2008 20:56:52 -0600 (CST) Christoph Lameter <cl@linux-foundation.org> 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.

  reply	other threads:[~2008-11-05 16:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-05  2:56 Git next: Second stage of cpu_alloc patches Christoph Lameter
2008-11-05  3:52 ` Andrew Morton
2008-11-05  7:26   ` Stephen Rothwell
2008-11-05  7:52     ` Vegard Nossum
2008-11-05 13:59       ` Christoph Lameter
2008-11-05 13:54   ` Christoph Lameter
2008-11-05 16:27     ` Andrew Morton [this message]
2008-11-05 21:12       ` Vegard Nossum
2008-11-05 21:24         ` Andrew Morton
2008-11-05 23:58     ` Johannes Weiner
2008-11-06  0:54       ` Stephen Rothwell
2008-11-06 14:54         ` Christoph Lameter

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=20081105082754.2d41f0d1.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=cl@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=travis@sgi.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.