Linux 5.7 rc1

It's Sunday afternoon, and it's been two weeks since the merge windowopened, so here we are. Maybe an hour or two early, because it'sEaster Sunday, and I may be socially distancing but we're still doingthe usual Finnish Easter dinner with lamb, mämma and pasha... I maynot be religious, but tradition is tradition. Thanks to the socialdistancing, this year we'll have to forgo trying to force-feed ourpoor American friends mämma, which never really works out anyway. Infact, I think I can hear the sighs of relief from miles away.Back to the kernel.Things looked pretty normal, in fact I felt things worked smootherthan they often do, with the bulk of the big pull requests all comingin the first week, just the way I prefer it. Yes, I had a fair numberof pulls the second week too, but a lot of them were smallersubsystems, or follow-ups, or fixes. Keeping people inside may havehelped.That said, we did have a couple of hiccups due to linux-next nothaving had some of the syzbot testing that it normally has, soimmediately when things hit my tree, a few alarm bells rang. Thatcertainly wasn't optimal. But it got sorted out quickly enough that itdidn't end up being all that painful, and hopefully we'll avoid thelack of test coverage in the future. At least there's a cunning planfor that. Knock wood.And things look normal stat-wise. Not the biggest kernel, not thesmallest, and the distribution of patches looks fairly regular too:about 60% drivers (all over - it's the merge window, after all) withthe rest being architecture updates (x86 and arm stand out, butthere's a little bit of everything), Documentation updates (more rstconversions, but also just regular updates), filesystem work (pathnamelookup cleanups and the new exfat filesystem stand out), networkingand "misc core kernel" work.As always, there's much too much new stuff to list with a shortlog, soappended is my mergelog.I did have a request from the kernel technical advisory board (akaTAB) to mention that if anyone's had (or is predicting) disruptions totheir kernel work from COVID-19 that they'd like help solving (findingbackup maintainers, etc), the kernel TAB has offered to help howeverthey can. If this would be useful, please contact them at:tab@lists.linux-foundation.orgAnything else?Oh, yeah. Go test.