diff mbox

[34/41] Documentation: dev-osd.rst: Fix some issues due to conversion

Message ID 1818691f50582b89ebbc2a75c6d2dd993f560c2b.1467670142.git.mchehab@s-opensource.com (mailing list archive)
State New, archived
Headers show

Commit Message

Mauro Carvalho Chehab July 5, 2016, 1:31 a.m. UTC 
The conversion to ReST broke a minor things. Fix them.

While here, also make EBUSY constant, just like on other places.

Signed-off-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>
---
 Documentation/linux_tv/media/v4l/dev-osd.rst | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)
diff mbox

Patch

diff --git a/Documentation/linux_tv/media/v4l/dev-osd.rst b/Documentation/linux_tv/media/v4l/dev-osd.rst
index 6a6ead6df54d..b9b53fd7eb5d 100644
--- a/Documentation/linux_tv/media/v4l/dev-osd.rst
+++ b/Documentation/linux_tv/media/v4l/dev-osd.rst
@@ -6,8 +6,8 @@ 
 Video Output Overlay Interface
 ******************************
 
-
 **Also known as On-Screen Display (OSD)**
+
 Some video output devices can overlay a framebuffer image onto the
 outgoing video signal. Applications can set up such an overlay using
 this interface, which borrows structures and ioctls of the
@@ -48,10 +48,11 @@  the ``linux/fb.h`` header file.
 The width and height of the framebuffer depends on the current video
 standard. A V4L2 driver may reject attempts to change the video standard
 (or any other ioctl which would imply a framebuffer size change) with an
-EBUSY error code until all applications closed the framebuffer device.
+``EBUSY`` error code until all applications closed the framebuffer device.
 
 
 .. code-block:: c
+    :caption: Example 4.1. Finding a framebuffer device for OSD
 
     #include <linux/fb.h>