libweston: rename weston_output_destroy() to weston_output_release()
authorPekka Paalanen <pekka.paalanen@collabora.co.uk>
Wed, 16 Aug 2017 09:07:14 +0000 (12:07 +0300)
committerPekka Paalanen <pekka.paalanen@collabora.co.uk>
Wed, 4 Oct 2017 13:18:06 +0000 (16:18 +0300)
commitae6d35db140afc303753972447e0125465997fe7
treee3c20ce94583e1a7a683326ea1fb4a435c77fb9e
parent01e0068868a2424aa53c5df9849f0aaa43b5bf37
libweston: rename weston_output_destroy() to weston_output_release()

'release' is a more appropriate name because the function does not free
the underlying memory. The main reason for this is that we need the name
weston_output_destroy() for new API that actually will free also the
underlying memory.

Since the function is only used in backends and external backends are
not a thing, this does not cause libweston major version bump, even
though it does change the ABI. There is no way external users could have
successfully used this function.

Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.co.uk>
Reviewed-by: Ian Ray <ian.ray@ge.com>
Acked-by Daniel Stone <daniels@collabora.com>
libweston/compositor-drm.c
libweston/compositor-fbdev.c
libweston/compositor-headless.c
libweston/compositor-rdp.c
libweston/compositor-wayland.c
libweston/compositor-x11.c
libweston/compositor.c
libweston/compositor.h