From: Hans Verkuil <hverkuil@xs4all.nl>
To: Prabhakar Lad <prabhakar.csengg@gmail.com>
Cc: LMML <linux-media@vger.kernel.org>,
DLOS <davinci-linux-open-source@linux.davincidsp.com>,
LKML <linux-kernel@vger.kernel.org>,
Hans Verkuil <hans.verkuil@cisco.com>,
Mauro Carvalho Chehab <m.chehab@samsung.com>
Subject: Re: [PATCH 1/2] media: davinci: vpif capture: upgrade the driver with v4l offerings
Date: Tue, 01 Apr 2014 08:40:16 +0200 [thread overview]
Message-ID: <533A5F50.30105@xs4all.nl> (raw)
In-Reply-To: <CA+V-a8s_mZNEuN0JHH_rpJU=zab57Q_LfLT_onwj0=ykgoUm0g@mail.gmail.com>
On 03/31/2014 07:24 PM, Prabhakar Lad wrote:
> Hi Hans,
>
> On Mon, Mar 31, 2014 at 8:34 PM, Hans Verkuil <hverkuil@xs4all.nl> wrote:
>> Hi Prabhakar,
>>
>> This looks really nice!
>>
> Writing a video driver has become really easy with almost 90% of work
> done by v4l core itself :)
That was the idea!
>> I'll do a full review on Friday, but in the meantime can you post the output
> OK.
>
>> of 'v4l2-compliance -s' using the latest v4l2-compliance version? I've made
>> some commits today, so you need to do a git pull of v4l-utils.git.
>>
> I had compilation failures for v4l2-compliance following is the patch
> fixing that, (I am
> facing some issues in cross compilation once done I'll post the o/p of it)
I fixed the 'friend' issue (weird that it didn't fail with my g++) and the other
issue was already fixed yesterday.
Regards,
Hans
next prev parent reply other threads:[~2014-04-01 6:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-31 14:52 [PATCH 0/2] DaVinci: VPIF: upgrade with v4l helpers Lad, Prabhakar
2014-03-31 14:52 ` [PATCH 1/2] media: davinci: vpif capture: upgrade the driver with v4l offerings Lad, Prabhakar
2014-03-31 15:04 ` Hans Verkuil
2014-03-31 17:24 ` Prabhakar Lad
2014-04-01 6:40 ` Hans Verkuil [this message]
2014-03-31 14:52 ` [PATCH 2/2] media: davinci: vpif display: " Lad, Prabhakar
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=533A5F50.30105@xs4all.nl \
--to=hverkuil@xs4all.nl \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=hans.verkuil@cisco.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=m.chehab@samsung.com \
--cc=prabhakar.csengg@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