Linux 5.10 rc1

wo weeks have passed, and the merge window is over. I've tagged andpushed out 5.10-rc1, and everything looks fairly normal.This looks to be a bigger release than I expected, and while the mergewindow is smaller than the one for 5.8 was, it's not a *lot* smaller.And 5.8 was our biggest release ever.I'm not entirely sure whether this is just a general upward trend (wedid seem to plateau for a while there), or just a fluke, or perhapsdue to 5.9 dragging out an extra week. We will see, I guess.That said, things seem to have gone fairly smoothly. I don't see anyhuge red flags, and the merge window didn't cause any unusual issuesfor me. Famous last words..The most interesting - to me - change here is Christoph's setf_fs()removal (it got merged through Al Viro, as you can see in my mergelogbelow).  It's not a _huge_ change, but it's interesting because thewhole model of set_fs() to specify whether a userspace copy actuallygoes to user space or kernel space goes back to pretty much theoriginal release of Linux, and while the name is entirely historic (ithasn't used the %fs segment register in a long time), the concept hasremained. Until now.We still do have "set_fs()" around, and not every architecture hasbeen converted to the new world order, but x86, powerpc, s390 andRISC-V have had the address space overrides removed, and all the corework is done. Other architectures will hopefully get converted awayfrom that very historic model too, but it might take a while to getrid of it all.Anyway, to most people that all shouldn't matter at all, and it'smainly a small historical footnote that 5.10 no longer relies on thewhole set_fs() model. Most of the actual changes are - as usual -driver updates, but there are changes all over. I think the merge logbelow gives some kind of flavor of what's been going on on a highlevel, but if you're interested in the details go look at the gittree. As mentioned, it's a big merge window, with  almost 14k commits(*) by closer to 1700 people.Please go test,                  Linus