diff options
author | Leandro Ribeiro <leandrohr@riseup.net> | 2020-01-27 19:12:01 -0300 |
---|---|---|
committer | Leandro Ribeiro <leandrohr@riseup.net> | 2020-01-29 12:15:16 -0300 |
commit | ca640d51203a7b7f1237af79e6ba4e5608333356 (patch) | |
tree | 8c0e404605c686ee4b733a624f4d7bc8ae479c01 /doc | |
parent | 4ec38d18b335de42e7560d59b98ba021e9a029d4 (diff) | |
download | weston-ca640d51203a7b7f1237af79e6ba4e5608333356.tar.gz |
libweston: fold weston_compositor_tear_down() into weston_compositor_destroy()
The only reason why we have both weston_compositor_tear_down() and
weston_compositor_destroy() is that the only we had to destroy
the log context was keeping weston_compositor alive and calling
weston_log_ctx_compositor_destroy().
After commit "weston-log: replace weston_log_ctx_compositor_destroy()
by weston_log_ctx_destroy()", it's not necessary to keep a zombie
weston_compositor just to be able to call
weston_log_ctx_compositor_destroy().
Fold weston_compositor_tear_down() into weston_compositor_destroy(),
as this split is useless now.
Signed-off-by: Leandro Ribeiro <leandrohr@riseup.net>
Diffstat (limited to 'doc')
-rw-r--r-- | doc/sphinx/toc/libweston/compositor.rst | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/sphinx/toc/libweston/compositor.rst b/doc/sphinx/toc/libweston/compositor.rst index 4fc1f57d..755d781f 100644 --- a/doc/sphinx/toc/libweston/compositor.rst +++ b/doc/sphinx/toc/libweston/compositor.rst @@ -4,8 +4,8 @@ Compositor :type:`weston_compositor` represents the core object of the library, which aggregates all the other objects and maintains their state. You can create it using :func:`weston_compositor_create`, while for releasing all the resources -associated with it, you should use :func:`weston_compositor_tear_down`, -followed by :func:`weston_compositor_destroy` to destroy it. +associated with it and then destroy it, you should use +:func:`weston_compositor_destroy`. Compositor API -------------- |