Linux 4.20 rc5

Hmm.. I'd like to say it was a normal week, but I'd be lying. rc5 isthe biggest rc so far (with the obvious exception of rc1), and itlooks fairly unusual in the diffstat too, with almost a third beingarch updates. Yes, another third is drivers (normal), but even therealmost half is in sound. The rest is tooling, mm, core networking andsome fs updates.So it all looks a bit odd, although none of it is hugely _alarming_.One of the reasons the arch side is a bit bigger than usual at thisstage is that we got the STIPB performance regression sorted out, forexample.But rc5 being somewhat bigger than you'd like is a good reason to lookat the timing for rest of the rc's. In particular, counting forwardthe usual three weeks, and you the calendar lights up with theholidays at around the time I'd expect to do a final 4.20 release.  Icertainly don't want to do a merge window during the holidays, sowe'll have to see how this goes.  But I'll be traveling the latterhalf of January, so I don't want to delay the merge window too lateeither.But I also don't want to have people do their final prep for the nextmerge window over the holidays, and then open the merge window rightafter. That likely just messes with all the submaintainers instead.So my current suggestion is that we plan on a Christmas release,everybody gets their pull requests for the next merge window done*before* the holidays, and then we see what happens. I think we allwant to have a calm holiday season without either the stress of amerge window _or_ the stress of prepping for one..Of course, if it doesn't calm down after this rc, that can force myhand and I may just have to delay the release regardless. But peoplecan get their ducks lined up for the next release before xmasregardless...                     Linus