Linux 4.19 rc1

So two weeks have passed, and the merge window for 4.19 is over.This was a fairly frustrating merge window, partly because 4.19 looksto be a pretty big release (no single reason), and partly just due torandom noise. We had the L1TF hw vulnerability disclosure early in themerge window, which just added the usual frustration due to havingpatches that weren't public. That just shows just how good all ourinfrastructure for linux-next and various automated testing systemshave become, in how painful it is when it's lacking.At least we didn't actually have a lot of problems on that front inthe mainline kernel, there seemed to be many more pain points in thebackports.We also had a report of a TLB shootdown bug come in during this mergewindow, and while the patches for ended up not being a huge problem,TLB invalidation issues is actually one of the things that stresses meout. They're really nasty to debug (thanks to Jann Horn forpinpointing this one), and our interfaces to the architecture specificroutines are subtle and pretty complicated. And messy. I think thediscussion will result in a few cleanups later, but timing could havebeen so much better for this.Oh well. I guess I can partly just blame myself for having delayed4.18 by a week, which just made everything happen during that firstand busiest week of the merge window. Bad luck. Although even thesecond week - when things usually calm down - was also pretty busythis time around.Anyway, on to the actual changes. And there' a lot of them. There'sjust a lot of things going on, and while this isn't the biggestrelease we've had (4.9 still keeps that crown), this does join 4.12and 4.15 as one of the bigger kernel releases, at least just judgingby number of commits in the merge window.As usual, there's way too many patches to list even in shortlogformat, but appended is my usual "mergelog" of people I merged fromand a one-liner overview of the merge. There's actually a couple ofpull requests that I might still look at after the merge window, butthat are probably in the "there's always the next one" pile.The "big picture" of the merge window looks pretty normal: just undertwo thirds of the changes are to drivers (gpu and network driversbeing the bulk - as usual), with the rest being architecture updates(all the usual suspects), filesystems, core kernel and networking.There's a fair chunk of documentation and tooling updates too(selftests, tracing, perf..).Anyway, go forth and test,                 Linus