From: Sylwester Nawrocki <s.nawrocki@samsung.com>
To: Kamil Debski <k.debski@samsung.com>, linux-media@vger.kernel.org
Cc: arun.kk@samsung.com
Subject: Re: [PATCH] v4l: Fix documentation of V4L2_PIX_FMT_H264_MVC and VP8 pixel formats
Date: Wed, 14 May 2014 17:04:25 +0200 [thread overview]
Message-ID: <537385F9.2030809@samsung.com> (raw)
In-Reply-To: <1400077869-17573-1-git-send-email-k.debski@samsung.com>
On 14/05/14 16:31, Kamil Debski wrote:
> The 'Code' column in the documentation should provide the real fourcc
> code that is used. Changed the documentation to provide the fourcc
> defined in videodev2.h
>
> Signed-off-by: Kamil Debski <k.debski@samsung.com>
Acked-by: Sylwester Nawrocki <s.nawrocki@samsung.com>
> ---
> Documentation/DocBook/media/v4l/pixfmt.xml | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/DocBook/media/v4l/pixfmt.xml b/Documentation/DocBook/media/v4l/pixfmt.xml
> index ea514d6..91dcbc8 100644
> --- a/Documentation/DocBook/media/v4l/pixfmt.xml
> +++ b/Documentation/DocBook/media/v4l/pixfmt.xml
> @@ -772,7 +772,7 @@ extended control <constant>V4L2_CID_MPEG_STREAM_TYPE</constant>, see
> </row>
> <row id="V4L2-PIX-FMT-H264-MVC">
> <entry><constant>V4L2_PIX_FMT_H264_MVC</constant></entry>
> - <entry>'MVC'</entry>
> + <entry>'M264'</entry>
> <entry>H264 MVC video elementary stream.</entry>
> </row>
> <row id="V4L2-PIX-FMT-H263">
> @@ -812,7 +812,7 @@ extended control <constant>V4L2_CID_MPEG_STREAM_TYPE</constant>, see
> </row>
> <row id="V4L2-PIX-FMT-VP8">
> <entry><constant>V4L2_PIX_FMT_VP8</constant></entry>
> - <entry>'VP8'</entry>
> + <entry>'VP80'</entry>
> <entry>VP8 video elementary stream.</entry>
> </row>
> </tbody>
prev parent reply other threads:[~2014-05-14 15:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-14 14:31 [PATCH] v4l: Fix documentation of V4L2_PIX_FMT_H264_MVC and VP8 pixel formats Kamil Debski
2014-05-14 15:04 ` Sylwester Nawrocki [this message]
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=537385F9.2030809@samsung.com \
--to=s.nawrocki@samsung.com \
--cc=arun.kk@samsung.com \
--cc=k.debski@samsung.com \
--cc=linux-media@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.