public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 3.14-rc8
Date: Tue, 25 Mar 2014 04:38:44 -0400	[thread overview]
Message-ID: <20140325083844.GA2516@redhat.com> (raw)
In-Reply-To: <CA+55aFzFj_XMNha5gcDHfmLE_Jb-O2OpdTbZyQdarJnip1gSBQ@mail.gmail.com>

On Mon, Mar 24, 2014 at 07:40:06PM -0700, Linus Torvalds wrote:
 > I delayed things a day from my normal schedule, hoping I'd feel more
 > comfortable doing a 3.14 release, but that was not to be. So here's an
 > rc8, and I expect to do the final 3.14 release next weekend.
 > 
 > There wasn't that much scary stuff going on, but there's a few vfs
 > fixes still pending, and we did end up having some interesting core
 > fixes last week too (not new regressions, but newly detected by
 > Trinity. Kudos to Hugh Dickins for figuring them out and fixing the
 > causes). There's also some networking fixes and random noise (mainly
 > MIPS).  So I really wanted another week before release after all.

FWIW, since Hugh's heroic work nailing those bugs, I've managed to run
trinity for days since without problems[1]. As we discussed today at the VM summit,
Sasha has found a bunch of things in -next that may be a problem in .14 too, 
(and in fact I've hit one of those BUGONs once), but on the whole it's looking
a lot better.

	Dave

[1] Actually, I've since crashed my test box for stupid reasons now that
    I'm 3000 miles away from it until the end of the week, but I have a way better
    opinion of rc8 than I did of rc7.

	Dave


  reply	other threads:[~2014-03-25  8:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-25  2:40 Linux 3.14-rc8 Linus Torvalds
2014-03-25  8:38 ` Dave Jones [this message]
2014-03-25 20:36 ` Linux 3.14-rc8 (LXC broken) Andre Tomt
2014-03-25 21:32   ` Serge Hallyn
2014-03-26  3:02   ` Eric Paris

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=20140325083844.GA2516@redhat.com \
    --to=davej@redhat.com \
    --cc=linux-kernel@vger.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