@kernellogger @kees @vbabka I don't necessarily agree with the process in mm as it stands but this is how it works right now, that is a lack of objection and Andrew not finding major flaws = Andrew in effect approves, and unless it's a relative newcomer or otherwise he has reason not to want it, the series will get merged.

So it's representative of what will be in the next merge window (+ hotfixes not yet upstreamed for rc).

I'd like there to be more of a 'needs a tag from at least someone' rule in mm, but can't control that. It adds workload to people who have to act fast to stop stuff getting pulled in.

If we limited it to mm-stable or something then -next would be _miles_ behind what is going into the next merge window, and you'd also _not_ be stabilising as while not enough people test -next NOBODY tests mm-unstable so it'd become a pretty useless tree.

Again, I think the issue is that more people need to test against -next.