summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorLeandro Ribeiro <leandrohr@riseup.net>2019-12-18 15:21:03 -0300
committerLeandro Ribeiro <leandrohr@riseup.net>2020-01-27 13:42:42 -0300
commit5976dbbbb5bbdbae44880b5467b055a0a3aa83f1 (patch)
treecb1b9bd972bb35d5133870e9496a9f414d8f2157 /doc
parentee73105f50969620dc25373ead2a405956c1c4bc (diff)
downloadweston-5976dbbbb5bbdbae44880b5467b055a0a3aa83f1.tar.gz
weston-log: rename the confusing function name weston_compositor_add_log_scope()
There's a function named weston_compositor_add_log_scope() but it doesn't take a struct weston_compositor argument. Rename it to weston_log_ctx_add_log_scope(), as the log_scope is being added to a log_context. Also, bump libweston_major to 9. Signed-off-by: Leandro Ribeiro <leandrohr@riseup.net>
Diffstat (limited to 'doc')
-rw-r--r--doc/sphinx/toc/libweston/log.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/sphinx/toc/libweston/log.rst b/doc/sphinx/toc/libweston/log.rst
index fd68385f..e1b03337 100644
--- a/doc/sphinx/toc/libweston/log.rst
+++ b/doc/sphinx/toc/libweston/log.rst
@@ -28,7 +28,7 @@ Log scopes
A scope represents a source for a data stream (i.e., a producer). You'll require
one as a way to generate data. Creating a log scope is done using
-:func:`weston_compositor_add_log_scope()`. You can customize the scope
+:func:`weston_log_ctx_add_log_scope()`. You can customize the scope
behaviour and you'll require at least a name and a description for the
scope.