Re: [PATCH weston 16/21] compositor-fbdev: always destroy renderer-output on disable

2017-09-25 Thread Ray, Ian (GE Healthcare)
On 22/09/2017, 17.33, "wayland-devel on behalf of Pekka Paalanen" wrote: > > From: Pekka Paalanen > > If we pass the base->enabled test, then the renderer output is > guaranteed to be there, so we can just destroy it. > > Destroying it before unmap makes the sequence match better the enable

[PATCH weston 16/21] compositor-fbdev: always destroy renderer-output on disable

2017-09-22 Thread Pekka Paalanen
From: Pekka Paalanen If we pass the base->enabled test, then the renderer output is guaranteed to be there, so we can just destroy it. Destroying it before unmap makes the sequence match better the enable path. Signed-off-by: Pekka Paalanen --- libweston/compositor-fbdev.c | 4 +--- 1 file ch