Linux 5.6 rc1

The rc1 tag has been pushed out, and so the merge window for 5.6 is closed.This was actually a slightly smaller merge window than usual, but Ithink that what happened is simply that the holiday season impactednew development. It impacted the 5.5 rc series less than I hadexpected, but seems to instead have caused 5.6 to have slightly lessdevelopment than normal.Of course, "slightly less" is just that - we still have more than 10kcommits (11.5k if you count merges too). So it's not like it's tiny,and it's still _way_ too big to post full shortlogs or anything likethat. So below is my usual "mergelog" that shows my merges and whothey came from.And as always, note that my merge log shows who I merged from, whichis not necessarily at all who developed the code. There's more than1400 individual developers in there, and I always feel a bit bad byjust grouping things by top-level maintainer, but I've never found agood way to summarize the merge window development by author (like therc shortlogs are done). So I just keep mentioning this, to make itclear that this shows just _one_ side of the credits for getting codemerged.Apart from being slightly smaller than usual, the stats all lookfairly normal. About two thirds of the patch is drivers (and it's allover, but gpu and networking dominate as usual), with the rest beingthe usual mix of arch updates, documentation, filesystem updates,networking, tooling, and just misc core kernel updates. And none ofthat is in the least surprising or unusual.From an actual ABI perspective, I guess the openat2() support byAleksa might be worth mentioning - it's been in development for a longtime, and went through several revisions on the mailing lists. It'sseldom we end up adding some new interfaces to really core stuff, butthis makes it much easier to do some path resolution control in userspace - particularly for sandboxing, You can ask to do filename lookupwithout following symlinks, for example, or not following mountpoints.So it's much easier to write code that says "I have this untrustedpathname that I want to open - only open it if it doesn't jump out ofmy sandboxed area".But otherwise it all looks fairly normal. A couple of new specialtyfilesystems if you're into that kind of thing, you can see the bigpicture in the merge log below.Go forth and test,