public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	tj@kernel.org, linux-kernel@vger.kernel.org, kyle@mcmartin.ca
Subject: Re: [GIT PULL] percpu for 2.6.31
Date: Fri, 19 Jun 2009 08:49:11 +0200	[thread overview]
Message-ID: <20090619064911.GC8162@elte.hu> (raw)
In-Reply-To: <20090618143959.62858ef6.akpm@linux-foundation.org>


* Andrew Morton <akpm@linux-foundation.org> wrote:

> On Thu, 18 Jun 2009 14:22:20 -0700 (PDT)
> Linus Torvalds <torvalds@linux-foundation.org> wrote:
> 
> > On Thu, 18 Jun 2009, Tejun Heo wrote:
> > > 
> > > Please pull from percpu-for-linus git tree from:
> > > 
> > >     git://git.kernel.org/pub/scm/linux/kernel/git/tj/percpu.git for-linus
> > 
> > I'm very unhappy with this kind of crap.
> 
> AFACIT none of these patches have ever been in linux-next.  Half 
> or more of them turned up on the mailing list for the first time 
> two days ago and there's little evidence that anyone has even 
> looked at them.

Hm, i've seen many of them (for months literally) and you were 
definitely Cc:-ed to all of them. The new bits (which i think you 
are referring to) are not included in this series - only the old 
bits.

I even asked you about them a month ago, whether you'd want to pick 
Tejun's bits up into -mm because they are clearly generic VM patches 
and they seemed to be falling between the cracks for v2.6.31. I had 
two small bits of x86 relevant percpu patches which i'd gladly have 
bounced over to you.

Btw., it will be a lot of work for Tejun to go through another 3 
months with a patch-set of this magnitude:

  170 files changed, 653 insertions(+), 553 deletions(-)

and i suspect it will cause a fair amount of linux-next conflict 
resolution overhead as well. So Tejun, if you can get it tested 
please consider targeting it for this merge window still. I can
help out with some -tip testig if you want.

	Ingo

  parent reply	other threads:[~2009-06-19  6:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-18  8:07 [GIT PULL] percpu for 2.6.31 Tejun Heo
2009-06-18 21:22 ` Linus Torvalds
2009-06-18 21:39   ` Andrew Morton
2009-06-18 22:43     ` Tejun Heo
2009-06-19  6:49     ` Ingo Molnar [this message]
2009-06-18 22:33   ` Tejun Heo
2009-06-18 22:45     ` Tejun Heo
2009-06-19  1:47     ` Tejun Heo
2009-06-19  5:39       ` Ingo Molnar
2009-06-19 19:39         ` Linus Torvalds
2009-06-19 21:08           ` Ingo Molnar

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=20090619064911.GC8162@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@linux-foundation.org \
    --cc=kyle@mcmartin.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tj@kernel.org \
    --cc=torvalds@linux-foundation.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