Karicheri, Muralidharan wrote:
> Mauro,
>
>>> How to request sign-off? Do I only send patches
>>> to the person, not to the list?
>
> I think you have not answered this.
>> For the patches exchanged via the ML, I need some scriptable way to mark
>> them
>> as RFC at the Patchwork.
>>
>> So, addin
Mauro,
>> How to request sign-off? Do I only send patches
>> to the person, not to the list?
>
I think you have not answered this.
>For the patches exchanged via the ML, I need some scriptable way to mark
>them
>as RFC at the Patchwork.
>
>So, adding [RFC PATCH] or [PATCH RFC] works. It also wor
Karicheri, Muralidharan wrote:
> Mauro,
>
> If you scan the patch, you would see the status of this patch series.
Ok, but it is not script-able. So, I need to have an easy way to know when
a patch is still under discussion at the ML or if it is ready for merging.
I need something that I can wri
ailto:mche...@redhat.com]
>Sent: Monday, February 01, 2010 6:12 PM
>To: Karicheri, Muralidharan
>Cc: linux-media@vger.kernel.org
>Subject: Re: [PATCH v3 1/6] V4L - vpfe capture - header files for ISIF
>driver
>
>m-kariche...@ti.com wrote:
>> From: Murali Karicheri
>>
&
m-kariche...@ti.com wrote:
> From: Murali Karicheri
>
> This is the header file for ISIF driver on DM365. ISIF driver is equivalent
> to CCDC driver on DM355 and DM644x. This driver is tested for
> YUV capture from TVP514x driver. This patch contains the header files
> required for
> this drive
Hi Kevin,
This patch is already approved by the V4L sub system. I need to get your
approval for the arch part (patch #6). I have updated the clock handling
based on your comments against the last patch (adding clock alias)
I will request Mauro to merge the arch part via the v4l tree. I have a
dev
