Nothing particularly odd going on this merge window. I had some travel
in the middle of it, but to offset that I had a new faster test-build
setup, and most of the pull requests came in early (thank you) so my
travels didn't actually end up affecting the merge window all that
much.
We did have a few late pull requests too, but since that meshed fairly
well with my schedule as per above, and people generally made the
proper noises ("sorry for late pull request, I had good reasons: xyz")
I didn't mind this time. But let's try to not repeat that, ok?
Things look fairly normal. Just about two thirds of the patch is
drivers (all over), with the bulk of the rest being arch updates,
tooling, documentation and vfs/filesystem updates, of which there were
more than usual (the unicode tables for ext4 case insensitivity do end
up being a big part of the "bulk" side).
But there's core networking, kernel and vm changes too - it's just
that the other areas tend to simply be much bulkier. Drivers etc tend
to just have a ton more lines to them, if only by virtue of there
being so many of them (although admittedly also sometimes because some
drivers tend to just be very verbose and have a lot of register
definitions etc).
Size-wise things look fairly normal. 12k+ commits (plus another ~750
merge commits) is about normal for us by now. And hard to summarize in
a release email. So appended is obviously just the usual shortlog of
merges I did and their sources, for a kind of overview of the _areas_
that have changed, rather than any real detail. You'll need to go look
at the git tree to see the details.
Go forth and test,
Linus
