damage: Make damageRegionProcessPending take a damage not a drawableperformance

In the case where there's no damage monitor on the drawable, we look
that fact up twice: once before rendering to decide whether to compute
damage, and again after to decide whether to append it. The layer below
us is effectively not allowed to change whether there's a damage monitor
for the drawable, but there's no way the compiler can know that.

Instead, look it up once up front, and change the check macros and
damageRegionProcessPending to refer to it.

Signed-off-by: Adam Jackson <ajax@redhat.com>

0 files changed, 0 insertions, 0 deletions