From: Hans Verkuil <hverkuil@xs4all.nl>
To: Robert Jarzmik <robert.jarzmik@free.fr>,
Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
Linux Media Mailing List <linux-media@vger.kernel.org>,
Josh Wu <josh.wu@atmel.com>
Subject: Re: [RFC] Move some soc-camera drivers to staging in preparation for removal
Date: Sun, 21 Feb 2016 16:06:13 +0100 [thread overview]
Message-ID: <56C9D265.50905@xs4all.nl> (raw)
In-Reply-To: <87h9h3xe1c.fsf@belgarion.home>
On 02/20/2016 10:33 PM, Robert Jarzmik wrote:
> Hans Verkuil <hverkuil@xs4all.nl> writes:
>
>>> pxa27x_camera is actively maintained, the latest submission request for merge
>>> is 11 days ago :
>>> https://lkml.org/lkml/2016/2/8/789
>>>
>>> I can submit a patch in MAINTAINERS if you wish to take it in my bucket.
>>
>> Please do! That's an easy patch, and then it is clear someone is actively maintaining
>> this.
> I prepared the patch.
>
> Now the question is : how will handle the pxa_camera patches, ie. taking them
> through his tree ?
>
> I'm under the impression that Guennadi is very busy, so for the MAINTAINERS
> patch as for the next ones, which tree will be handling them ? Moreover as most
> probably I will be the biggest contributor, who will be reviewing me ?
Guennadi is the soc-camera maintainer. So once pxa_camera no longer uses soc-camera
('independent v4l2 host') it would be me who would review the code and manages
patches.
BTW, where can I get pxa hardware? It is always nice if I am able to test code
as well. But I haven't been able to find a source for this platform.
Regards,
Hans
> We might also pave a path of Guennadi's point (3), ie. have pxa_camera "become
> independent V4L2 host".
>
>> BTW, vb1 refers to videobuf-core.h whereas vb2 refers to its successor videobuf2-core.h
>> and videobuf2-v4l2.h. The vb2 framework is vastly superior and integrates nicely with
>> dmabuf for buffer sharing between hardware components.
> Ok, I'll have a look too.
>
> Cheers.
>
> --
> Robert
>
next prev parent reply other threads:[~2016-02-21 17:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-19 13:24 [RFC] Move some soc-camera drivers to staging in preparation for removal Hans Verkuil
2016-02-19 16:24 ` Mauro Carvalho Chehab
2016-02-19 16:30 ` Hans Verkuil
2016-02-19 18:01 ` Robert Jarzmik
2016-02-19 18:12 ` Hans Verkuil
2016-02-20 21:33 ` Robert Jarzmik
2016-02-21 15:06 ` Hans Verkuil [this message]
2016-02-22 7:01 ` Guennadi Liakhovetski
2016-02-22 7:11 ` Guennadi Liakhovetski
2016-02-22 13:21 ` Laurent Pinchart
2016-02-22 13:39 ` Guennadi Liakhovetski
2016-02-22 14:23 ` Laurent Pinchart
2016-02-22 16:08 ` Ludovic Desroches
2016-02-23 7:06 ` Wu, Songjun
2016-02-23 7:26 ` Hans Verkuil
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=56C9D265.50905@xs4all.nl \
--to=hverkuil@xs4all.nl \
--cc=g.liakhovetski@gmx.de \
--cc=josh.wu@atmel.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@osg.samsung.com \
--cc=robert.jarzmik@free.fr \
/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.