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.18-rc6
Date: Sun, 23 Nov 2014 19:25:21 -0500 [thread overview]
Message-ID: <20141124002521.GA25241@redhat.com> (raw)
In-Reply-To: <CA+55aFx7PYp=a2FnpnvYy1jDHsvLsJDpO88KycPgEa3gmJwG7A@mail.gmail.com>
On Sun, Nov 23, 2014 at 04:08:21PM -0800, Linus Torvalds wrote:
> Really not a whole lot of code changed, and if it wasn't for the
> pending trouble from DaveJ, I'd probably be perfectly happy. Let's see
> how that all unfolds, but in the meantime, the more testing this can
> get, the better.
FYI, I gave 3.17 + perf fixes ~36 hours of runtime before calling it
good on Friday. Since then I've started a bisect, and I'm about 3 builds
deep on that, with 9-10 to go. 2 of the bad builds took the better part
of a day to hit, with the third happening in just an hour.
Hopefully I get more of the latter kind, and we can wrap this up this
week, though thanksgiving may upset things.
Dave
prev parent reply other threads:[~2014-11-24 0:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-24 0:08 Linux 3.18-rc6 Linus Torvalds
2014-11-24 0:25 ` Dave Jones [this message]
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=20141124002521.GA25241@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