From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: linux-media@vger.kernel.org,
sakari.ailus@maxwell.research.nokia.com,
Hans Verkuil <hverkuil@xs4all.nl>
Subject: Re: [RFC/PATCH v3 0/7] V4L2 subdev userspace API
Date: Wed, 04 Aug 2010 12:38:04 -0300 [thread overview]
Message-ID: <4C59895C.5090709@infradead.org> (raw)
In-Reply-To: <201008041446.24894.laurent.pinchart@ideasonboard.com>
Em 04-08-2010 09:46, Laurent Pinchart escreveu:
> Hi,
>
> On Monday 12 July 2010 17:25:45 Laurent Pinchart wrote:
>> Hi everybody,
>>
>> Here's the third version of the V4L2 subdev userspace API patches. Comments
>> received on the first and second versions have been incorporated, including
>> the video_usercopy usage. The generic ioctls support patch has been
>> dropped and will be resubmitted later with a use case.
>
> Mauro, is there a chance those patches could get in 2.6.36 ?
Unfortunately, the changes are not high.
I still have lots of patches ready to merge that I received before the start of the
merge window waiting for me to handle. As you know, we should first send the patches
to linux-next, and wait for a while, before sending them upstream. I won't doubt that
this time, we'll have only a 7-days window before -rc1.
There are also some other dead lines for this week, including the review of LPC proposals.
Finally, one requirement for merging API additions is to have a driver using it.
In the past, we had bad experiences of adding things at the kernel API, but waiting
for a very long time for a kernel driver using it, as the ones that pushed hard for
adding the new API's didn't submitted their drivers timely (on some cased it ended by
having a driver using the new API's several kernel versions later).
So, even considering that subdev API is ready, we still need to wait for drivers needing
it to be submitted. So, the better is to analyse and apply it after the end of the merge window,
on a separate branch, merging it at the main branch after receiving a driver needing
the new API.
Cheers,
Mauro.
next prev parent reply other threads:[~2010-08-04 15:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-12 15:25 [RFC/PATCH v3 0/7] V4L2 subdev userspace API Laurent Pinchart
2010-07-12 15:25 ` [RFC/PATCH v3 1/7] v4l: Share code between video_usercopy and video_ioctl2 Laurent Pinchart
2010-08-04 18:30 ` Hans Verkuil
2010-08-04 19:37 ` Laurent Pinchart
2010-07-12 15:25 ` [RFC/PATCH v3 2/7] v4l: subdev: Don't require core operations Laurent Pinchart
2010-08-04 18:30 ` Hans Verkuil
2010-07-12 15:25 ` [RFC/PATCH v3 3/7] v4l: subdev: Merge v4l2_i2c_new_subdev_cfg and v4l2_i2c_new_subdev Laurent Pinchart
2010-08-04 18:30 ` Hans Verkuil
2010-07-12 15:25 ` [RFC/PATCH v3 4/7] v4l: subdev: Add device node support Laurent Pinchart
2010-08-04 18:34 ` Hans Verkuil
2010-07-12 15:25 ` [RFC/PATCH v3 5/7] v4l: subdev: Uninline the v4l2_subdev_init function Laurent Pinchart
2010-08-04 18:35 ` Hans Verkuil
2010-07-12 15:25 ` [RFC/PATCH v3 6/7] v4l: subdev: Control ioctls support Laurent Pinchart
2010-08-04 18:37 ` Hans Verkuil
2010-07-12 15:25 ` [RFC/PATCH v3 7/7] v4l: subdev: Events support Laurent Pinchart
2010-08-04 18:37 ` Hans Verkuil
2010-08-04 12:46 ` [RFC/PATCH v3 0/7] V4L2 subdev userspace API Laurent Pinchart
2010-08-04 15:38 ` Mauro Carvalho Chehab [this message]
2010-08-04 20:29 ` Laurent Pinchart
2010-08-04 20:56 ` 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=4C59895C.5090709@infradead.org \
--to=mchehab@infradead.org \
--cc=hverkuil@xs4all.nl \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=sakari.ailus@maxwell.research.nokia.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