From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: linux-doc@vger.kernel.org, mchehab@s-opensource.com
Cc: linux-media@vger.kernel.org, mchehab@infradead.org,
linux-kernel@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Hans Verkuil <hans.verkuil@cisco.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Aviv Greenberg <aviv.d.greenberg@intel.com>
Subject: [PATCH 1/1] docs-rst: media: Don't use \small for V4L2_PIX_FMT_SRGGB10 documentation
Date: Sun, 3 Sep 2017 23:12:33 +0300 [thread overview]
Message-ID: <20170903201233.31638-1-sakari.ailus@linux.intel.com> (raw)
In-Reply-To: <82fc5322d611390dca21f28e3fd5f7cbe0c27be4.1504464984.git.mchehab@s-opensource.com>
There appears to be an issue in using \small in certain cases on Sphinx
1.4 and 1.5. Other format documents don't use \small either, remove it
from here as well.
Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>
---
Hi Mauro,
What would you think of this as an alternative approach? No hacks needed.
Just a recognition \small could have issues. For what it's worth, I
couldn't reproduce the issue on Sphinx 1.4.9.
Regards,
Sakari
Documentation/media/uapi/v4l/pixfmt-srggb10p.rst | 11 -----------
1 file changed, 11 deletions(-)
diff --git a/Documentation/media/uapi/v4l/pixfmt-srggb10p.rst b/Documentation/media/uapi/v4l/pixfmt-srggb10p.rst
index 86cd07e5bfa3..368ee61ab209 100644
--- a/Documentation/media/uapi/v4l/pixfmt-srggb10p.rst
+++ b/Documentation/media/uapi/v4l/pixfmt-srggb10p.rst
@@ -33,13 +33,6 @@ of a small V4L2_PIX_FMT_SBGGR10P image:
**Byte Order.**
Each cell is one byte.
-
-.. raw:: latex
-
- \small
-
-.. tabularcolumns:: |p{2.0cm}|p{1.0cm}|p{1.0cm}|p{1.0cm}|p{1.0cm}|p{10.0cm}|
-
.. flat-table::
:header-rows: 0
:stub-columns: 0
@@ -73,7 +66,3 @@ Each cell is one byte.
- R\ :sub:`33high`
- R\ :sub:`33low`\ (bits 7--6) G\ :sub:`32low`\ (bits 5--4)
R\ :sub:`31low`\ (bits 3--2) G\ :sub:`30low`\ (bits 1--0)
-
-.. raw:: latex
-
- \normalsize
--
2.11.0
next prev parent reply other threads:[~2017-09-03 20:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-03 19:03 [PATCH 0/7] Another set of fixes for PDF output Mauro Carvalho Chehab
2017-09-03 19:03 ` [PATCH 1/7] media: format.rst: use the right markup for important notes Mauro Carvalho Chehab
2017-09-03 19:03 ` [PATCH 2/7] media: v4l2 uapi book: get rid of driver programming's chapter Mauro Carvalho Chehab
2017-09-03 19:03 ` [PATCH 3/7] media: vivid.rst: add a blank line to correct ReST format Mauro Carvalho Chehab
2017-09-03 19:03 ` [PATCH 4/7] media: vidioc-g-fmt.rst: adjust table format Mauro Carvalho Chehab
2017-09-03 19:03 ` [PATCH 5/7] media: fix build breakage with Sphinx 1.6 Mauro Carvalho Chehab
2017-09-03 20:12 ` Sakari Ailus [this message]
2017-09-04 1:40 ` [PATCH 1/1] docs-rst: media: Don't use \small for V4L2_PIX_FMT_SRGGB10 documentation Mauro Carvalho Chehab
2017-09-04 20:43 ` Mauro Carvalho Chehab
2017-09-03 19:03 ` [PATCH 6/7] media: pixfmt*.rst: replace a two dots by a comma Mauro Carvalho Chehab
2017-09-03 19:03 ` [PATCH 7/7] media: index.rst: don't write "Contents:" on PDF output Mauro Carvalho Chehab
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170903201233.31638-1-sakari.ailus@linux.intel.com \
--to=sakari.ailus@linux.intel.com \
--cc=aviv.d.greenberg@intel.com \
--cc=corbet@lwn.net \
--cc=hans.verkuil@cisco.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=mchehab@s-opensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox