Linux 5.10 Released

Ok, here it is - 5.10 is tagged and pushed out.I pretty much always wish that the last week was even calmer than itwas, and that's true here too. There's a fair amount of fixes in here,including a few last-minute reverts for things that didn't get fixed,but nothing makes me go "we need another week". Things look fairlynormal.It's mostly drivers - as it should be - with a smattering of fixes allover: networking, architectures, filesystems, tooling.. The shortlogis appended, and scanning it gives a good idea of what kind of thingsare there. Nothing that looks scary: most of the patches are verysmall, and the biggest one is fixing pin mapping definitions for apincontrol driver.This also obviously means that the merge window for 5.11 will starttomorrow.  I already have a couple of pull requests pending - you guysknow who you are, and thank you.The most notable thing about the 5.11 merge window will be obvious toanybody who takes a look at the calendar: realistically speaking, weonly have one week before the holidays are upon us, and everybody ismuch too distracted. That means that I will be particularly strictabout the whole "the merge window is for things that are ready*before* the merge window starts".Now, I'm sure you all want to go off for holidays too, and I'mactually surprised that I don't have more early pull requests pending.So I think the whole "everything you send me should have already beendone" is something we can all sign up for. But exactly _because_ ofthe timing, I will simply not be very interested in any new late pullrequests that come in the second week of the merge window: I expect tostill be handling some of the backlog that week _anyway_, but Icertainly do not want to get more of it.So if it's not already in linux-next, and if you aren't happy sendingit in this upcoming week because it's not quite done yet, you shouldbasically plan on not getting it into 5.11 at all. There will bereleases after that one, don't worry.This has _technically_ been the rule before too, it's just that Igenerally haven't been all that hard-nosed about it, and have letthings slide if it wasn't _too_ egregious. This time around I havefairly clear reasons why I'm just going to enforce that "it had betterbe ready before the merge window even opened" rule.If my overflow handling then ends up being interrupted by theholidays, I may end up delaying rc1 just to catch up, but I hope andexpect that that won't even be needed. We'll see. But even if it doeshappen, it most certainly will _not_ mean that I will take pullrequests that came in after the holidays.Actual fixes that would be valid even outside the merge window areobviously not affected by that rule.             Linus