[PATCH 3/7] compositor: activity happens in core scope only

[Tiago Vignatti]

Only input events generate activity to wake up and unlock the compositor -
that's the theory at least for now, and this doesn't require any backend
knowledge. Note that the act of hotplug the device itself won't awake the
compositor, but the _activity_ of the new device will -- we're okay.

So make such procedure static to the core compositor.

Signed-off-by: Tiago Vignatti <tiago.vignatti at intel.com>
---
 src/compositor.c |    2 +-
 src/compositor.h |    2 --
 2 files changed, 1 insertions(+), 3 deletions(-)

diff --git a/src/compositor.c b/src/compositor.c
index 4cd8d99..a607772 100644
--- a/src/compositor.c
+++ b/src/compositor.c
@@ -1418,7 +1418,7 @@ weston_compositor_wake(struct weston_compositor *compositor)
 				     compositor->idle_time * 1000);
 }
 
-WL_EXPORT void
+static void
 weston_compositor_activity(struct weston_compositor *compositor)
 {
 	if (compositor->state == WESTON_COMPOSITOR_ACTIVE) {
diff --git a/src/compositor.h b/src/compositor.h
index d4f85d4..fc46b10 100644
--- a/src/compositor.h
+++ b/src/compositor.h
@@ -373,8 +373,6 @@ weston_compositor_unlock(struct weston_compositor *compositor);
 void
 weston_compositor_wake(struct weston_compositor *compositor);
 void
-weston_compositor_activity(struct weston_compositor *compositor);
-void
 weston_compositor_update_drag_surfaces(struct weston_compositor *compositor);
 
 
-- 
1.7.5.4