From: Sakari Ailus <sakari.ailus@iki.fi>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
linux-media@vger.kernel.org
Cc: Julien BERAUD <julien.beraud@parrot.com>,
Boris Todorov <boris.st.todorov@gmail.com>,
Gary Thomas <gary@mlbassoc.com>,
Enrico <ebutera@users.berlios.de>,
Stefan Herbrechtsmeier <sherbrec@cit-ec.uni-bielefeld.de>,
Javier Martinez Canillas <martinez.javier@gmail.com>,
Chris Whittenburg <whittenburg@gmail.com>
Subject: Re: [PATCH 00/11] OMAP3 ISP BT.656 support
Date: Tue, 27 May 2014 00:18:40 +0300 [thread overview]
Message-ID: <5383AFB0.9070703@iki.fi> (raw)
In-Reply-To: <1401133812-8745-1-git-send-email-laurent.pinchart@ideasonboard.com>
Hi Laurent,
Laurent Pinchart wrote:
> Hello,
>
> This patch sets implements support for BT.656 and interlaced formats in the
> OMAP3 ISP driver. Better late than never I suppose, although given how long
> this has been on my to-do list there's probably no valid excuse.
Thanks!
Acked-by: Sakari Ailus <sakari.ailus@iki.fi>
--
Sakari Ailus
sakari.ailus@iki.fi
next prev parent reply other threads:[~2014-05-26 21:18 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-26 19:50 [PATCH 00/11] OMAP3 ISP BT.656 support Laurent Pinchart
2014-05-26 19:50 ` [PATCH 01/11] v4l: subdev: Extend default link validation to cover field order Laurent Pinchart
2014-05-26 19:50 ` [PATCH 02/11] omap3isp: Don't ignore subdev streamoff failures Laurent Pinchart
2014-05-26 19:50 ` [PATCH 03/11] omap3isp: Remove boilerplate disclaimer and FSF address Laurent Pinchart
2014-05-26 19:50 ` [PATCH 04/11] omap3isp: Move non-critical code out of the mutex-protected section Laurent Pinchart
2014-05-26 19:50 ` [PATCH 05/11] omap3isp: Default to progressive field order when setting the format Laurent Pinchart
2014-05-26 19:50 ` [PATCH 06/11] omap3isp: video: Validate the video node field order Laurent Pinchart
2014-05-26 19:50 ` [PATCH 07/11] omap3isp: ccdc: Simplify the configuration function Laurent Pinchart
2014-05-26 19:50 ` [PATCH 08/11] omap3isp: ccdc: Simplify the ccdc_isr_buffer() function Laurent Pinchart
2014-05-26 19:50 ` [PATCH 09/11] omap3isp: ccdc: Add basic support for interlaced video Laurent Pinchart
2014-05-26 21:12 ` Sakari Ailus
2014-05-26 19:50 ` [PATCH 10/11] omap3isp: ccdc: Support the interlaced field orders at the CCDC output Laurent Pinchart
2014-05-26 19:50 ` [PATCH 11/11] omap3isp: ccdc: Add support for BT.656 YUV format at the CCDC input Laurent Pinchart
2014-05-26 21:18 ` Sakari Ailus [this message]
2014-05-27 8:38 ` [PATCH 00/11] OMAP3 ISP BT.656 support Enrico
2014-06-24 15:19 ` Enrico
2014-06-24 17:19 ` Stefan Herbrechtsmeier
2014-07-01 20:24 ` Laurent Pinchart
2014-07-04 11:21 ` Stefan Herbrechtsmeier
2014-06-26 16:18 ` Enrico
2014-07-01 20:17 ` Laurent Pinchart
2014-07-22 15:52 ` Enrico
2014-07-22 16:04 ` Laurent Pinchart
2014-07-22 16:26 ` Enrico
2014-07-22 16:32 ` Laurent Pinchart
2014-07-23 13:54 ` Enrico
2014-07-23 13:57 ` Enrico
2014-07-30 21:01 ` Laurent Pinchart
2014-07-31 10:21 ` Enrico
2014-08-01 13:46 ` Laurent Pinchart
[not found] ` <1406046034.73192.YahooMailNeo@web162404.mail.bf1.yahoo.com>
2014-07-22 16:27 ` 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=5383AFB0.9070703@iki.fi \
--to=sakari.ailus@iki.fi \
--cc=boris.st.todorov@gmail.com \
--cc=ebutera@users.berlios.de \
--cc=gary@mlbassoc.com \
--cc=julien.beraud@parrot.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=martinez.javier@gmail.com \
--cc=sherbrec@cit-ec.uni-bielefeld.de \
--cc=whittenburg@gmail.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).