Code review comment for lp://staging/~vanvugt/mir/fix-buffers_ready_for_compositor

#2: Fair enough, I think the unified approach is something to work towards, but in the meantime, we may as well use this approach to solve the problem. Keeping track of whether the stack is damaged seems a better concept than what's in trunk or the wakeup and keep-running-until-drained approach.

#1: I guess I'd like to pause this branch to avoid breaking downstream in a way that we don't have a fix for yet. Its mostly just a timing issue, but I'd guess that the Belgium sprinters might want to integrate the tip of mir with the tip of the other components.

So anyways, approve from me, but would appreciate pausing the branch until we have a downstream update available.