summaryrefslogtreecommitdiff
path: root/Documentation/media/uapi/cec/cec-ioc-dqevent.rst
diff options
context:
space:
mode:
authorMauro Carvalho Chehab <mchehab@s-opensource.com>2016-08-19 11:14:23 -0300
committerMauro Carvalho Chehab <mchehab@s-opensource.com>2016-08-22 10:31:51 -0300
commitfa92b04d98e7c52038c1eb1cbf89ba0ba8679a94 (patch)
treee5519f1c53c35b4c0716de9e5835a349651b9d84 /Documentation/media/uapi/cec/cec-ioc-dqevent.rst
parent42858b555292196a49b08f03a6e63758ac90a482 (diff)
[media] docs-rst: fix warnings introduced by LaTeX patchset
Sphinx is really pedantic with respect to the order where table tags and references are created. Putting things at the wrong order causes troubles. The order that seems to work is: .. raw:: latex .. tabularcolumns:: .. _foo_name: .. cssclass: longtable .. flat-table:: Reorder the tags to the above order, to avoid troubles, and fix remaining warnings introduced by media recent patches. Signed-off-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>
Diffstat (limited to 'Documentation/media/uapi/cec/cec-ioc-dqevent.rst')
-rw-r--r--Documentation/media/uapi/cec/cec-ioc-dqevent.rst15
1 files changed, 5 insertions, 10 deletions
diff --git a/Documentation/media/uapi/cec/cec-ioc-dqevent.rst b/Documentation/media/uapi/cec/cec-ioc-dqevent.rst
index c27b56881a4a..f606d2ffe6a9 100644
--- a/Documentation/media/uapi/cec/cec-ioc-dqevent.rst
+++ b/Documentation/media/uapi/cec/cec-ioc-dqevent.rst
@@ -51,11 +51,10 @@ 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.
+.. tabularcolumns:: |p{1.2cm}|p{2.9cm}|p{13.4cm}|
.. _cec-event-state-change_s:
-.. tabularcolumns:: |p{1.2cm}|p{2.9cm}|p{13.4cm}|
-
.. flat-table:: struct cec_event_state_change
:header-rows: 0
:stub-columns: 0
@@ -79,11 +78,10 @@ it is guaranteed that the state did change in between the two events.
- The current set of claimed logical addresses.
+.. tabularcolumns:: |p{1.0cm}|p{2.0cm}|p{14.5cm}|
.. _cec-event-lost-msgs_s:
-.. tabularcolumns:: |p{1.0cm}|p{2.0cm}|p{14.5cm}|
-
.. flat-table:: struct cec_event_lost_msgs
:header-rows: 0
:stub-columns: 0
@@ -107,11 +105,10 @@ it is guaranteed that the state did change in between the two events.
this is more than enough.
+.. tabularcolumns:: |p{1.0cm}|p{4.2cm}|p{2.5cm}|p{8.8cm}|
.. _cec-event:
-.. tabularcolumns:: |p{1.0cm}|p{4.2cm}|p{2.5cm}|p{8.8cm}|
-
.. flat-table:: struct cec_event
:header-rows: 0
:stub-columns: 0
@@ -175,11 +172,10 @@ it is guaranteed that the state did change in between the two events.
event.
+.. tabularcolumns:: |p{5.6cm}|p{0.9cm}|p{11.0cm}|
.. _cec-events:
-.. tabularcolumns:: |p{5.6cm}|p{0.9cm}|p{11.0cm}|
-
.. flat-table:: CEC Events Types
:header-rows: 0
:stub-columns: 0
@@ -206,11 +202,10 @@ it is guaranteed that the state did change in between the two events.
application didn't dequeue CEC messages fast enough.
+.. tabularcolumns:: |p{6.0cm}|p{0.6cm}|p{10.9cm}|
.. _cec-event-flags:
-.. tabularcolumns:: |p{6.0cm}|p{0.6cm}|p{10.9cm}|
-
.. flat-table:: CEC Event Flags
:header-rows: 0
:stub-columns: 0