From: Andrew Morton <akpm@linux-foundation.org>
To: Christoph Lameter <clameter@sgi.com>
Cc: Pekka Enberg <penberg@cs.helsinki.fi>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] slub: remove duplicate VM_BUG_ON
Date: Wed, 2 May 2007 14:27:56 -0700 [thread overview]
Message-ID: <20070502142756.de29ab08.akpm@linux-foundation.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0705021413570.2469@schroedinger.engr.sgi.com>
On Wed, 2 May 2007 14:14:39 -0700 (PDT)
Christoph Lameter <clameter@sgi.com> wrote:
> On Wed, 2 May 2007, Pekka Enberg wrote:
>
> > Christoph Lameter wrote:
> > > Patch is already in mm. Could you download all the patches after that before
> > > testing? There was quite a number.
> >
> > I am on 2.6.21-rc7-mm2. Me goes to wonder where Andrew's snapshots are...
>
> Too much going on I think. I guess I saturated him with patches.
>
yes, I'm very much in "slow things down, do it more carefully" mode. I
have 350 patches sitting awaiting later consideration at present.
It's not so much that I'm personally swamped - it's more that I think we've
hit (exceeded) the rate at which we can feed stuff into the tree while
maintaining acceptable quality.
If others were to increase the amount of time they spend on testing,
reviewing and bugfixing it would help to level things out.
I should have got the 2.6.22-mm-merge-plans email out a week or two
earlier, I'm afraid. Things are looking somewhat messy.
next prev parent reply other threads:[~2007-05-02 21:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-02 20:08 [PATCH] slub: remove duplicate VM_BUG_ON Pekka J Enberg
2007-05-02 20:12 ` Christoph Lameter
2007-05-02 20:21 ` Pekka Enberg
2007-05-02 21:14 ` Christoph Lameter
2007-05-02 21:27 ` Andrew Morton [this message]
2007-05-02 21:42 ` Current SLUB Tree 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=20070502142756.de29ab08.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=clameter@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
/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