From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: linux-media@vger.kernel.org
Cc: mchehab@s-opensource.com, yong.zhi@intel.com
Subject: [PATCH 1/2] v4l: Fix references in Intel IPU3 Bayer documentation
Date: Fri, 29 Dec 2017 14:59:13 +0200 [thread overview]
Message-ID: <20171229125914.7218-2-sakari.ailus@linux.intel.com> (raw)
In-Reply-To: <20171229125914.7218-1-sakari.ailus@linux.intel.com>
The references in Intel IPU3 Bayer format documentation were wrong. Fix
them.
Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>
---
Documentation/media/uapi/v4l/pixfmt-srggb10-ipu3.rst | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/Documentation/media/uapi/v4l/pixfmt-srggb10-ipu3.rst b/Documentation/media/uapi/v4l/pixfmt-srggb10-ipu3.rst
index 72fbd8f96381..99cde5077519 100644
--- a/Documentation/media/uapi/v4l/pixfmt-srggb10-ipu3.rst
+++ b/Documentation/media/uapi/v4l/pixfmt-srggb10-ipu3.rst
@@ -1,9 +1,9 @@
.. -*- coding: utf-8; mode: rst -*-
-.. _V4L2_PIX_FMT_IPU3_SBGGR10:
-.. _V4L2_PIX_FMT_IPU3_SGBRG10:
-.. _V4L2_PIX_FMT_IPU3_SGRBG10:
-.. _V4L2_PIX_FMT_IPU3_SRGGB10:
+.. _v4l2-pix-fmt-ipu3-sbggr10:
+.. _v4l2-pix-fmt-ipu3-sgbrg10:
+.. _v4l2-pix-fmt-ipu3-sgrbg10:
+.. _v4l2-pix-fmt-ipu3-srggb10:
**********************************************************************************************************************************************
V4L2_PIX_FMT_IPU3_SBGGR10 ('ip3b'), V4L2_PIX_FMT_IPU3_SGBRG10 ('ip3g'), V4L2_PIX_FMT_IPU3_SGRBG10 ('ip3G'), V4L2_PIX_FMT_IPU3_SRGGB10 ('ip3r')
--
2.11.0
next prev parent reply other threads:[~2017-12-29 12:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-29 12:59 [PATCH 0/2] A few IPU3 CIO2 fixes Sakari Ailus
2017-12-29 12:59 ` Sakari Ailus [this message]
2017-12-29 12:59 ` [PATCH 2/2] intel-ipu3: Rename arr_size macro, use min Sakari Ailus
2017-12-29 13:42 ` [PATCH 0/2] A few IPU3 CIO2 fixes 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=20171229125914.7218-2-sakari.ailus@linux.intel.com \
--to=sakari.ailus@linux.intel.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@s-opensource.com \
--cc=yong.zhi@intel.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;
as well as URLs for NNTP newsgroup(s).