public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	mingo@elte.hu, linux-kernel@vger.kernel.org, kyle@mcmartin.ca
Subject: Re: [GIT PULL] percpu for 2.6.31
Date: Fri, 19 Jun 2009 07:43:51 +0900	[thread overview]
Message-ID: <4A3AC327.8020500@kernel.org> (raw)
In-Reply-To: <20090618143959.62858ef6.akpm@linux-foundation.org>

Hello, Andrew.

Andrew Morton 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.

Unfortunately, they grew out of their home so they didn't have proper
path to linux-next but I wasn't that careless.  The two patchsets went
through three and four revisions.

percpu-convert-most-archs-to-dynamic-percpu

    http://thread.gmane.org/gmane.linux.kernel.cross-arch/3818
    http://www.gossamer-threads.com/lists/linux/kernel/1083895
    http://thread.gmane.org/gmane.linux.kernel/839059

x86-percpu-fix-pageattr-handling

    http://thread.gmane.org/gmane.linux.kernel.cross-arch/3825
    http://thread.gmane.org/gmane.linux.kernel/844298
    http://article.gmane.org/gmane.linux.kernel/837157
    http://thread.gmane.org/gmane.linux.kernel/836771

> If this doesn't mean "you missed 2.6.31" then what does?
> 
> Yes, things like this can be messy and hard to develop and maintain
> outside the merge window.  We understand this.  There are special
> cases.  But when this happens, let's talk about it and see what we can
> do!  Please let's not pretend that this is an ordinary old git merge
> like all the others.

Sorry.  My fault.  It used to go through x86 and this was me realizing
that nobody was gonna take care of these patchsets and prepping trees
myself in a hurry.  Won't happen again.

Thanks.

-- 
tejun

  reply	other threads:[~2009-06-18 22:42 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 [this message]
2009-06-19  6:49     ` Ingo Molnar
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=4A3AC327.8020500@kernel.org \
    --to=tj@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=kyle@mcmartin.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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