All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 3.1-rc2
Date: Sun, 14 Aug 2011 16:38:35 -0700	[thread overview]
Message-ID: <CA+55aFznFY-j4cE29_JDgPNQixuFFNJn+pgo2WxBR1LXK=OkfQ@mail.gmail.com> (raw)
In-Reply-To: <CA+55aFycTvbuNzdgbHjoiNkTeDpzgu6Yf=vx9DU+PDOtC_17zA@mail.gmail.com>

On Sun, Aug 14, 2011 at 3:45 PM, Linus Torvalds
<torvalds@linux-foundation.org> wrote:
>
> That said, I would be happy if it calmed down further. 300+ commits
> for -rc2 is good, but please make me even happier for -rc3 by ONLY
> sending me real fixes. Think of it as "fairly late in the -rc series",
> because I really want to compensate for the merge window being fairly
> chaotic.

.. oh, and a couple of things I forgot to mention.

The mirroring from master.kernel.org to the public sites has been
pretty slow lately, and the main machine has been under a constant
load of about 35-50 for the last few days doing rsync checksumming or
something.

So it may not show up on the public sites for a while. I'm still not
seeing the stuff I pushed out early in the morning on git.kernel.org,
for example. So right now the delay seems to be in the 12+ hour range.

Developers who have direct access to master.kernel.org can obviously
see it, but...

The other thing I forgot to mention was that people are now actively
encouraged to test out SLUB debugging again. Not only is it always
nice to enable allocator debugging to find bugs elsewhere, but this
time it's doubly encouraged just to double- and triple-check that the
SLUB bugs that caused problems are gone. In addition to whatever bugs
elsewhere caught by redzoning and poisoning.

                Linus

  reply	other threads:[~2011-08-14 23:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-14 22:45 Linux 3.1-rc2 Linus Torvalds
2011-08-14 23:38 ` Linus Torvalds [this message]
2011-08-15  9:58 ` Paul Rolland
2011-08-15 17:18 ` [PATCH 3.1-rc2] x86: fix mm/fault.c build Randy Dunlap
2011-08-16  2:09   ` Linus Torvalds
2011-08-16  5:27     ` H. Peter Anvin
2011-08-16  6:00     ` Rule 1 (Was: Re: [PATCH 3.1-rc2] x86: fix mm/fault.c build) Stephen Rothwell
2011-08-16  6:20     ` [tip:x86/vdso] x86, vsyscall: Add missing <asm/fixmap.h> to arch/x86/mm/fault.c tip-bot for H. Peter Anvin
2011-08-16  6:43       ` Pekka Enberg
2011-08-16 15:02         ` H. Peter Anvin
2011-08-16 15:27     ` tip-bot for H. Peter Anvin
2011-08-16 17:23       ` Randy Dunlap
2011-08-16  4:41 ` [PATCH 3.1-rc2] xen: self-balloon needs module.h Randy Dunlap
2011-08-16  5:11   ` Konrad Rzeszutek Wilk

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='CA+55aFznFY-j4cE29_JDgPNQixuFFNJn+pgo2WxBR1LXK=OkfQ@mail.gmail.com' \
    --to=torvalds@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.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 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.