From: Sylwester Nawrocki <s.nawrocki@samsung.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: linux-fbdev@vger.kernel.org, linux-media@vger.kernel.org
Subject: Re: [PATCH v4 2/3] v4l: Add V4L2_PIX_FMT_NV24 and V4L2_PIX_FMT_NV42
Date: Tue, 29 Nov 2011 17:19:09 +0000 [thread overview]
Message-ID: <4ED5140D.4080200@samsung.com> (raw)
In-Reply-To: <1322562419-9934-3-git-send-email-laurent.pinchart@ideasonboard.com>
Hi Laurent,
On 11/29/2011 11:26 AM, Laurent Pinchart wrote:
> NV24 and NV42 are planar YCbCr 4:4:4 and YCrCb 4:4:4 formats with a
> luma plane followed by an interleaved chroma plane.
>
> Signed-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> ---
...
> + </example>
> + </refsect1>
> + </refentry>
> +
> + <!--
> +Local Variables:
> +mode: sgml
> +sgml-parent-document: "pixfmt.sgml"
> +indent-tabs-mode: nil
> +End:
> + -->
I think this comment chunk is redundant, it's just for emacs configuration.
Every time I open the file containing litter like this I get a not-so-useful
message, asking if I want to load the variables defined there or not.
I'm considering a patch cleaning up the Docbook from this emacs stuff, as I
also made a mistake copying this comment when adding NV12M, NV12MT formats.
Looks like most of people are doing that, e.g. see
http://www.mail-archive.com/linux-media@vger.kernel.org/msg38637.html
;)
--
Regards,
Sylwester
next prev parent reply other threads:[~2011-11-29 17:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-29 10:26 [PATCH v4 0/3] fbdev: Add FOURCC-based format configuration API Laurent Pinchart
2011-11-29 10:26 ` [PATCH v4 1/3] " Laurent Pinchart
2011-11-29 10:26 ` [PATCH v4 2/3] v4l: Add V4L2_PIX_FMT_NV24 and V4L2_PIX_FMT_NV42 formats Laurent Pinchart
2011-11-29 17:19 ` Sylwester Nawrocki [this message]
2011-11-29 18:11 ` Laurent Pinchart
2011-11-29 10:26 ` [PATCH v4 3/3] fbdev: sh_mobile_lcdc: Support FOURCC-based format API Laurent Pinchart
2011-12-12 16:08 ` [PATCH v4 0/3] fbdev: Add FOURCC-based format configuration API Laurent Pinchart
2011-12-12 18:49 ` Florian Tobias Schandinat
2011-12-13 0:40 ` Laurent Pinchart
2011-12-13 10:47 ` Geert Uytterhoeven
2011-12-13 11:46 ` Laurent Pinchart
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=4ED5140D.4080200@samsung.com \
--to=s.nawrocki@samsung.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-fbdev@vger.kernel.org \
--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 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).