From: Sakari Ailus <sakari.ailus@maxwell.research.nokia.com>
To: "linux-media@vger.kernel.org" <linux-media@vger.kernel.org>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Hans Verkuil <hverkuil@xs4all.nl>,
Cohen David Abraham <david.cohen@nokia.com>
Subject: [PATCH v7 0/6] V4L2 file handles and event interface
Date: Tue, 23 Feb 2010 01:01:30 +0200 [thread overview]
Message-ID: <4B830CCA.8030909@maxwell.research.nokia.com> (raw)
Hi,
Here's the ninth version of the V4L2 file handle and event interface
patchset.
The patchset has been tested with the OMAP 3 ISP driver. Patches for
OMAP 3 ISP are not part of this patchset but are available in Gitorious
(branch is called event):
git://gitorious.org/omap3camera/mainline.git event
The patchset I'm posting now is against the v4l-dvb tree instead of
linux-omap. The omap3camera tree thus has a slightly different
version of these patches due to different baselines.
Some more comments from Hans and Sergio. What has changed:
- Proper ioctl numbers!
- v4l2_fh_init() may now fail as v4l2_event_init() may also.
- Fixed copyright years.
- Fixed file names in file headings.
- Removed WARN_ON() in v4l2_event_init(). This function is only called
from v4l2_fh_init() and it also initialises the field related to WARN_ON().
- Documentation fixes suggested by Hans.
Comments are welcome as always.
Cheers,
--
Sakari Ailus
sakari.ailus@maxwell.research.nokia.com
next reply other threads:[~2010-02-22 23:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-22 23:01 Sakari Ailus [this message]
2010-02-22 23:01 ` [PATCH v7 1/6] V4L: File handles Sakari Ailus
2010-02-22 23:01 ` [PATCH v7 2/6] V4L: File handles: Add documentation Sakari Ailus
2010-02-22 23:01 ` [PATCH v7 3/6] V4L: Events: Add new ioctls for events Sakari Ailus
2010-02-22 23:01 ` [PATCH v7 4/6] V4L: Events: Add backend Sakari Ailus
2010-02-22 23:01 ` [PATCH v7 5/6] V4L: Events: Support event handling in do_ioctl Sakari Ailus
2010-02-22 23:01 ` [PATCH v7 6/6] V4L: Events: Add documentation Sakari Ailus
2010-02-22 23:40 ` Randy Dunlap
2010-02-24 16:34 ` Sakari Ailus
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=4B830CCA.8030909@maxwell.research.nokia.com \
--to=sakari.ailus@maxwell.research.nokia.com \
--cc=david.cohen@nokia.com \
--cc=hverkuil@xs4all.nl \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
/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.