[PATCH 2/7] damage: Simplify DamageUnregister

[Chris Wilson]

On Mon, Sep 02, 2013 at 10:18:57AM -0400, Adam Jackson wrote:
> You can only register one drawable on a given damage, so there's no
> reason to require the caller to specify the drawable, the damage is
> enough.  The implementation would do something fairly horrible if you
> _did_ pass mismatched drawable and damage, so let's avoid the problem
> entirely.
> 
> Signed-off-by: Adam Jackson <ajax at redhat.com>

And it makes xf86RotateDestroy() less terrifying!
Reviewed-by: Chris Wilson <chris at chris-wilson.co.uk>
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre