From: Guenter Roeck <linux@roeck-us.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 3.19-rc1 - merge window closed
Date: Sat, 20 Dec 2014 21:08:54 -0800 [thread overview]
Message-ID: <20141221050854.GA23583@roeck-us.net> (raw)
In-Reply-To: <CA+55aFwu19GP5vHTwadX+ygAKwOqNLuEBA9TVEdnfxgvzP1zHA@mail.gmail.com>
On Sat, Dec 20, 2014 at 05:43:22PM -0800, Linus Torvalds wrote:
> So it's been a day less than two weeks, and the merge window is closed.
>
> Considering how much came in fairly late, I find it hard to care about
> anybody who had decided to cut it even closer than some people already
> did. That said, maybe there aren't any real stragglers - and judging
> by the size of rc1, there really can't have been much. Not only do I
> think there are more commits than there were in linux-next, this is
> one of the bigger rc1's (at least by commits) historically. We've had
> bigger ones (3.10 and 3.15 both had large merge windows leading up to
> them), but this was definitely not a small merge window.
>
> Anyway, we've got changes all over the place, including a new
> architecture (nios2). My "short mergelog" is appended, and as usual I
> want to point out that that credits the people sending me the changes,
> which is generally not necessarily at all the same thing as the people
> actually writing the code, even if there is obviously overlap.
>
> In the "big picture", this looks like a fairly normal release. About
> two thirds driver updates, with about half of the rest being
> architecture updates (and no, the new nios2 patches are not at all
> dominant, it's about half ARM, with the new nios2 support being less
> than 10% of the arch updates by lines overall). The remaining one
> sixth is "misc": networking, header updates, documentation,
> filesystems, tooling, and core kernel (in pretty much that order).
>
> Obviously, with the holidays coming up, I'd expect that the next few
> weeks are pretty quiet, but we'll see. I do hope that people will have
> time to test this all in between all the eggnog,
>
There are at least the never-resting auto-testers, which for mine report:
Build tests:
total: 133 pass: 133 fail: 0
Qemu tests:
total: 30 pass: 30 fail: 0
Details at http://server.roeck-us.net:8010/builders.
This is an absolute first; since I started testing, we never had an
-rc1 with no build or qemu failures. Excellent job everyone!
Guenter
next prev parent reply other threads:[~2014-12-21 5:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-21 1:43 Linux 3.19-rc1 - merge window closed Linus Torvalds
2014-12-21 5:08 ` Guenter Roeck [this message]
2014-12-21 7:11 ` Nicholas A. Bellinger
2014-12-21 12:11 ` Guenter Roeck
2014-12-22 19:41 ` Nicholas A. Bellinger
2014-12-29 9:46 ` Guenter Roeck
2014-12-22 20:43 ` Andrew Morton
2014-12-22 20:56 ` Jiri Kosina
2014-12-22 22:43 ` Nicholas A. Bellinger
2014-12-22 23:02 ` Linus Torvalds
2014-12-22 23:22 ` Paul Bolle
2014-12-23 1:50 ` Sid Boyce
2014-12-23 10:07 ` Michal Marek
2014-12-22 23:08 ` Grant Coady
2014-12-21 21:00 ` Michael S. Tsirkin
[not found] <CAHse=S-CGRrXPZXooHsnqO6BJytBKE4t=V_ESHL1m6Gjzeg9GQ@mail.gmail.com>
2014-12-22 23:19 ` David Drysdale
2015-01-07 21:16 ` Michal Marek
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=20141221050854.GA23583@roeck-us.net \
--to=linux@roeck-us.net \
--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