From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Sylwester Nawrocki <snjw23@gmail.com>
Cc: linux-media@vger.kernel.org,
Sylwester Nawrocki <s.nawrocki@samsung.com>,
linux-samsung-soc@vger.kernel.org, m.szyprowski@samsung.com,
kyungmin.park@samsung.com, sw0312.kim@samsung.com,
riverful.kim@samsung.com
Subject: Re: [PATCH 0/19 v4] s5p-fimc driver conversion to media controller and control framework
Date: Tue, 06 Sep 2011 17:52:14 -0300 [thread overview]
Message-ID: <4E6687FE.5030607@redhat.com> (raw)
In-Reply-To: <4E6256B2.7010407@gmail.com>
Em 03-09-2011 13:32, Sylwester Nawrocki escreveu:
> On 09/01/2011 05:30 PM, Sylwester Nawrocki wrote:
>> Hello,
>>
>> following is a fourth version of the patchset converting s5p-fimc driver
>> to the media controller API and the new control framework.
>>
>> Mauro, could you please have a look at the patches and let me know of any doubts?
>> I tried to provide possibly detailed description of what each patch does and why.
>>
>> The changeset is available at:
>> http://git.infradead.org/users/kmpark/linux-2.6-samsung
>> branch: v4l_fimc_for_mauro
>>
>> on top of patches from Marek's 'Videobuf2& FIMC fixes" pull request
>> which this series depends on.
> ...
>>
>> Sylwester Nawrocki (19):
>> s5p-fimc: Remove registration of video nodes from probe()
>> s5p-fimc: Remove sclk_cam clock handling
>> s5p-fimc: Limit number of available inputs to one
>> s5p-fimc: Remove sensor management code from FIMC capture driver
>> s5p-fimc: Remove v4l2_device from video capture and m2m driver
>> s5p-fimc: Add the media device driver
>> s5p-fimc: Conversion to use struct v4l2_fh
>> s5p-fimc: Convert to the new control framework
>> s5p-fimc: Add media operations in the capture entity driver
>> s5p-fimc: Add PM helper function for streaming control
>> s5p-fimc: Correct color format enumeration
>> s5p-fimc: Convert to use media pipeline operations
>> s5p-fimc: Add subdev for the FIMC processing block
>> s5p-fimc: Add support for JPEG capture
>> s5p-fimc: Add v4l2_device notification support for single frame
>> capture
>> s5p-fimc: Use consistent names for the buffer list functions
>> s5p-fimc: Add runtime PM support in the camera capture driver
>> s5p-fimc: Correct crop offset alignment on exynos4
>> s5p-fimc: Remove single-planar capability flags
>
> oops, I've done this posting wrong, the first patch is missing here :(
> -> s5p-fimc: Add media entity initialization
>
> Still the patch set is complete at git repository as indicated above.
> I'm sorry for the confusion.
No problem. I always check from git.
Patches applied, thanks!
Mauro
>
> --
> Regards,
> Sylwester
>
>
>
>
>
next prev parent reply other threads:[~2011-09-06 20:52 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-01 15:30 [PATCH 0/19 v4] s5p-fimc driver conversion to media controller and control framework Sylwester Nawrocki
2011-09-01 15:30 ` [PATCH 01/19 v4] s5p-fimc: Remove registration of video nodes from probe() Sylwester Nawrocki
2011-09-01 15:30 ` [PATCH 02/19 v4] s5p-fimc: Remove sclk_cam clock handling Sylwester Nawrocki
2011-09-01 15:30 ` [PATCH 03/19 v4] s5p-fimc: Limit number of available inputs to one Sylwester Nawrocki
2011-09-01 15:30 ` [PATCH 04/19 v4] s5p-fimc: Remove sensor management code from FIMC capture driver Sylwester Nawrocki
2011-09-01 15:30 ` [PATCH 05/19 v4] s5p-fimc: Remove v4l2_device from video capture and m2m driver Sylwester Nawrocki
2011-09-01 15:30 ` [PATCH 06/19 v4] s5p-fimc: Add the media device driver Sylwester Nawrocki
2011-09-01 15:30 ` [PATCH 07/19 v4] s5p-fimc: Conversion to use struct v4l2_fh Sylwester Nawrocki
2011-09-01 15:30 ` [PATCH 08/19 v4] s5p-fimc: Convert to the new control framework Sylwester Nawrocki
2011-09-01 15:30 ` [PATCH 09/19 v4] s5p-fimc: Add media operations in the capture entity driver Sylwester Nawrocki
2011-09-01 15:30 ` [PATCH 10/19 v4] s5p-fimc: Add PM helper function for streaming control Sylwester Nawrocki
2011-09-01 15:30 ` [PATCH 11/19 v4] s5p-fimc: Correct color format enumeration Sylwester Nawrocki
2011-09-01 15:30 ` [PATCH 12/19 v4] s5p-fimc: Convert to use media pipeline operations Sylwester Nawrocki
2011-09-01 15:30 ` [PATCH 13/19 v4] s5p-fimc: Add subdev for the FIMC processing block Sylwester Nawrocki
2011-09-01 15:30 ` [PATCH 14/19 v4] s5p-fimc: Add support for JPEG capture Sylwester Nawrocki
2011-09-01 15:30 ` [PATCH 15/19 v4] s5p-fimc: Add v4l2_device notification support for single frame capture Sylwester Nawrocki
2011-09-01 15:30 ` [PATCH 16/19 v4] s5p-fimc: Use consistent names for the buffer list functions Sylwester Nawrocki
2011-09-01 15:30 ` [PATCH 17/19 v4] s5p-fimc: Add runtime PM support in the camera capture driver Sylwester Nawrocki
2011-09-01 15:30 ` [PATCH 18/19 v4] s5p-fimc: Correct crop offset alignment on exynos4 Sylwester Nawrocki
2011-09-01 15:30 ` [PATCH 19/19 v4] s5p-fimc: Remove single-planar capability flags Sylwester Nawrocki
2011-09-03 16:32 ` [PATCH 0/19 v4] s5p-fimc driver conversion to media controller and control framework Sylwester Nawrocki
2011-09-06 20:52 ` Mauro Carvalho Chehab [this message]
2011-09-08 6:48 ` Sylwester Nawrocki
2011-09-08 8:23 ` 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=4E6687FE.5030607@redhat.com \
--to=mchehab@redhat.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=riverful.kim@samsung.com \
--cc=s.nawrocki@samsung.com \
--cc=snjw23@gmail.com \
--cc=sw0312.kim@samsung.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 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.