One small point on this - I don't necessarily blame you for wrapping up some other stuff in review with the rebase, BUT - it makes difficult for reviewers when it comes to picking up changes between v13 and v14.
You're going to have issues anyway given the flurry of THP patches we get every cycle, but part of the review process often is to use git range-diff to check what _actually_ change between revisions. And in this case, I had to resolve a whole bunch of merge conflicts just to get v13 to a point where it _kind of_ represents what was there before on a common base. Obviously I'm not asking you to constantly rebase series :P but I'd say in future it might be useful to separate out the rebase step from the respin, when asked for a resend to just do a resend, THEN if the time is right for a respin, to do that separately. Really more applicable to larger series like this and it's all a bit fuzzy, but in this case it definitely would have helped! Thanks, Lorenzo
