[PATCH] Call flush callback chain when we flush client buffer due to overflow

[Dave Airlie]

>> Also, there is one more call to FlushClient in CloseDownConnection; any
>> reason we shouldn't be invoking the FlushCallback there too? More from a
>> sense of completeness than a chance that it's going to actually matter.
>
> Yes, that sounds fine.  And I just realized that we need to change the
> damageext handler to report damage after, so the batch buffer will
> already have the rendering in it, in case writing the event overflows
> the output buffers.  I'll roll these changes into an updated patch and
> resend
>

Just from memory, we changed the damage reporting order before (not
sure if you are talking about same thing here) and it fixed one set of
problems but broke swcursor on dri apps I think.

Dave.