wayland-drm: remove wl_buffer.damage
authorPekka Paalanen <ppaalanen@gmail.com>
Tue, 10 Apr 2012 12:35:06 +0000 (15:35 +0300)
committerKristian Høgsberg <krh@bitplanet.net>
Tue, 10 Apr 2012 17:06:56 +0000 (13:06 -0400)
commit272bc489762c6946e3c0314e9e035b281c567310
treebdcbdca78a1145b00f221b40e52945bd27841c9b
parent70d038e46eb877ffa922003c78630eb7eb76c0f3
wayland-drm: remove wl_buffer.damage

This is a related fix for the Wayland change:

commit 83685c506e76212ae4e5cb722205d98d3b0603b9
Author: Kristian Høgsberg <krh@bitplanet.net>
Date:   Mon Mar 26 16:33:24 2012 -0400

    Remove wl_buffer.damage and simplify shm implementation

Apparently, this should also fix a memory leak. When wl_buffer.damage
was removed from Wayland and Mesa was not fixed, wl_buffer.destroy ended
up in the (empty) damage function instead of calling
wl_resource_destroy().

Spotted during build as:
  CC     wayland-drm-protocol.lo
wayland-drm.c:80:2: warning: initialization from incompatible pointer type
wayland-drm.c:82:1: warning: excess elements in struct initializer
wayland-drm.c:82:1: warning: (near initialization for 'drm_buffer_interface')

Signed-off-by: Pekka Paalanen <ppaalanen@gmail.com>
src/egl/wayland/wayland-drm/wayland-drm.c