Commit 39b6b900 authored by Mauro Carvalho Chehab's avatar Mauro Carvalho Chehab

[media] fix clock_gettime cross-references

Fix those warnings:

	Documentation/media/uapi/cec/cec-ioc-dqevent.rst:124: WARNING: c:func reference target not found: clock_gettime(2)

By replacing it with the right function name, using this shell script:

	for i in `find Documentation/media -type f`; do sed 's,clock_gettime(2),clock_gettime,' <$i >a && mv a $i; done

Please notice that this will make the nitpick mode to shut up
complaining about that, becasue clock_gettime is on its exclude list,
but the cross reference will be undefined until someone documents
this function at the core documentation.
Signed-off-by: default avatarMauro Carvalho Chehab <mchehab@s-opensource.com>
parent a17a954e
...@@ -122,7 +122,7 @@ it is guaranteed that the state did change in between the two events. ...@@ -122,7 +122,7 @@ it is guaranteed that the state did change in between the two events.
- :cspan:`1` Timestamp of the event in ns. - :cspan:`1` Timestamp of the event in ns.
The timestamp has been taken from the ``CLOCK_MONOTONIC`` clock. To access The timestamp has been taken from the ``CLOCK_MONOTONIC`` clock. To access
the same clock from userspace use :c:func:`clock_gettime(2)`. the same clock from userspace use :c:func:`clock_gettime`.
- .. row 2 - .. row 2
......
...@@ -95,7 +95,7 @@ result. ...@@ -95,7 +95,7 @@ result.
- Timestamp in ns of when the last byte of the message was transmitted. - Timestamp in ns of when the last byte of the message was transmitted.
The timestamp has been taken from the ``CLOCK_MONOTONIC`` clock. To access The timestamp has been taken from the ``CLOCK_MONOTONIC`` clock. To access
the same clock from userspace use :c:func:`clock_gettime(2)`. the same clock from userspace use :c:func:`clock_gettime`.
- .. row 2 - .. row 2
...@@ -105,7 +105,7 @@ result. ...@@ -105,7 +105,7 @@ result.
- Timestamp in ns of when the last byte of the message was received. - Timestamp in ns of when the last byte of the message was received.
The timestamp has been taken from the ``CLOCK_MONOTONIC`` clock. To access The timestamp has been taken from the ``CLOCK_MONOTONIC`` clock. To access
the same clock from userspace use :c:func:`clock_gettime(2)`. the same clock from userspace use :c:func:`clock_gettime`.
- .. row 3 - .. row 3
......
...@@ -712,7 +712,7 @@ Buffer Flags ...@@ -712,7 +712,7 @@ Buffer Flags
clock). Monotonic clock has been favoured in embedded systems clock). Monotonic clock has been favoured in embedded systems
whereas most of the drivers use the realtime clock. Either kinds whereas most of the drivers use the realtime clock. Either kinds
of timestamps are available in user space via of timestamps are available in user space via
:c:func:`clock_gettime(2)` using clock IDs ``CLOCK_MONOTONIC`` :c:func:`clock_gettime` using clock IDs ``CLOCK_MONOTONIC``
and ``CLOCK_REALTIME``, respectively. and ``CLOCK_REALTIME``, respectively.
- .. _`V4L2-BUF-FLAG-TIMESTAMP-MONOTONIC`: - .. _`V4L2-BUF-FLAG-TIMESTAMP-MONOTONIC`:
...@@ -723,7 +723,7 @@ Buffer Flags ...@@ -723,7 +723,7 @@ Buffer Flags
- The buffer timestamp has been taken from the ``CLOCK_MONOTONIC`` - The buffer timestamp has been taken from the ``CLOCK_MONOTONIC``
clock. To access the same clock outside V4L2, use clock. To access the same clock outside V4L2, use
:c:func:`clock_gettime(2)`. :c:func:`clock_gettime`.
- .. _`V4L2-BUF-FLAG-TIMESTAMP-COPY`: - .. _`V4L2-BUF-FLAG-TIMESTAMP-COPY`:
......
...@@ -152,7 +152,7 @@ call. ...@@ -152,7 +152,7 @@ call.
- -
- Event timestamp. The timestamp has been taken from the - Event timestamp. The timestamp has been taken from the
``CLOCK_MONOTONIC`` clock. To access the same clock outside V4L2, ``CLOCK_MONOTONIC`` clock. To access the same clock outside V4L2,
use :c:func:`clock_gettime(2)`. use :c:func:`clock_gettime`.
- .. row 12 - .. row 12
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment