summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMauro Carvalho Chehab <mchehab@s-opensource.com>2016-07-13 15:22:38 +0200
committerMauro Carvalho Chehab <mchehab@s-opensource.com>2016-07-13 15:56:27 +0200
commitcc0fe5cd980dda7524e99882197682dcc3193db5 (patch)
treea5d1fc9ffe21487f5889a2e2981f3a0e1698accf
parent[media] doc-rst: improve CEC documentation (diff)
downloadlinux-cc0fe5cd980dda7524e99882197682dcc3193db5.tar.xz
linux-cc0fe5cd980dda7524e99882197682dcc3193db5.zip
[media] doc-rst: fix an undefined reference
Documentation/media/uapi/cec/cec-ioc-dqevent.rst:43: WARNING: undefined label: cec_event_state_change (if the link has no caption the label must precede a section header) Signed-off-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>
-rw-r--r--Documentation/media/uapi/cec/cec-ioc-dqevent.rst6
1 files changed, 3 insertions, 3 deletions
diff --git a/Documentation/media/uapi/cec/cec-ioc-dqevent.rst b/Documentation/media/uapi/cec/cec-ioc-dqevent.rst
index 0fdd4afa8d82..2785a4cb9f08 100644
--- a/Documentation/media/uapi/cec/cec-ioc-dqevent.rst
+++ b/Documentation/media/uapi/cec/cec-ioc-dqevent.rst
@@ -45,9 +45,9 @@ there is no more room in a queue then the last event is overwritten with
the new one. This means that intermediate results can be thrown away but
that the latest event is always available. This also means that is it
possible to read two successive events that have the same value (e.g.
-two :ref:`CEC_EVENT_STATE_CHANGE <CEC_EVENT_STATE_CHANGE>` events with the same state). In that case
-the intermediate state changes were lost but it is guaranteed that the
-state did change in between the two events.
+two :ref:`CEC_EVENT_STATE_CHANGE <CEC-EVENT-STATE-CHANGE>` events with
+the same state). In that case the intermediate state changes were lost but
+it is guaranteed that the state did change in between the two events.
.. _cec-event-state-change_s: