From: Sakari Ailus <sakari.ailus@maxwell.research.nokia.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: linux-media@vger.kernel.org
Subject: Re: [PATCH FOR 2.6.35] v4l: event: Export the v4l2_event_init and v4l2_event_dequeue functions
Date: Sun, 02 May 2010 20:46:35 +0300 [thread overview]
Message-ID: <4BDDBA7B.3000907@maxwell.research.nokia.com> (raw)
In-Reply-To: <1272821563-7946-1-git-send-email-laurent.pinchart@ideasonboard.com>
Laurent Pinchart wrote:
> Signed-off-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> ---
> drivers/media/video/v4l2-event.c | 2 ++
> 1 files changed, 2 insertions(+), 0 deletions(-)
>
> Sakari, this should go to 2.6.35 with the V4L2 events patch set. Could you ack
> the patch so that Mauro can apply it to his linux-next tree ?
Thanks for the patch, Laurent!
I understand this should go in to allow drivers not using video_ioctl2()
to support events as well, right?
Thus,
Acked-by: Sakari Ailus <sakari.ailus@maxwell.research.nokia.com>
> Regards,
>
> Laurent Pinchart
>
> diff --git a/drivers/media/video/v4l2-event.c b/drivers/media/video/v4l2-event.c
> index 170e40f..2e673fb 100644
> --- a/drivers/media/video/v4l2-event.c
> +++ b/drivers/media/video/v4l2-event.c
> @@ -45,6 +45,7 @@ int v4l2_event_init(struct v4l2_fh *fh)
>
> return 0;
> }
> +EXPORT_SYMBOL_GPL(v4l2_event_init);
>
> int v4l2_event_alloc(struct v4l2_fh *fh, unsigned int n)
> {
> @@ -144,6 +145,7 @@ int v4l2_event_dequeue(struct v4l2_fh *fh, struct v4l2_event *event,
>
> return ret;
> }
> +EXPORT_SYMBOL_GPL(v4l2_event_dequeue);
>
> /* Caller must hold fh->event->lock! */
> static struct v4l2_subscribed_event *v4l2_event_subscribed(
--
Sakari Ailus
sakari.ailus@maxwell.research.nokia.com
prev parent reply other threads:[~2010-05-02 17:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-02 17:32 [PATCH FOR 2.6.35] v4l: event: Export the v4l2_event_init and v4l2_event_dequeue functions Laurent Pinchart
2010-05-02 17:46 ` Sakari Ailus [this message]
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=4BDDBA7B.3000907@maxwell.research.nokia.com \
--to=sakari.ailus@maxwell.research.nokia.com \
--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.