All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Hans Verkuil <hverkuil@xs4all.nl>,
	linux-media <linux-media@vger.kernel.org>
Subject: Re: [GIT PULL FOR v3.5] Update v4l2-dev/ioctl.c to add gspca locking requirements
Date: Thu, 10 May 2012 19:57:52 +0200	[thread overview]
Message-ID: <4FAC01A0.2050105@redhat.com> (raw)
In-Reply-To: <1517975.APt9bbvSEu@avalon>

Hi,

On 05/10/2012 05:35 PM, Laurent Pinchart wrote:
> Hi Hans,
>
> On Thursday 10 May 2012 13:59:34 Hans Verkuil wrote:
>> Hi Mauro,
>>
>> Here is the pull request for this. HdG's gspca work depends on this and he
>> likes to get this in for 3.5. I think these are pretty good improvements
>> and for 3.6 I intend to build on it, basically getting rid of the whole
>> huge switch statement in v4l2-ioctl.c and replace it with table look-ups
>> and callbacks.
>>
>> But for now this is primarily to support the gspca work.
>
> The patches have been posted as RFCs early today and the pull request is
> already here... I'd like to review them first if you don't mind :-)

I reviewed and acked them (Hans V. has addressed my one concern on irc),
of course having multiple reviewers is good, so go ahead. Note that there
is not a real lot of interesting stuff inside though wrt potential locking
issues as the old behavior is preserved.

This patch just allows for drivers to selective opt out of the video_device
/ v4l2-dev.c lock for certain ioctls and for all non ioctl fops.

Regards,

Hans

      reply	other threads:[~2012-05-10 17:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-10 11:59 [GIT PULL FOR v3.5] Update v4l2-dev/ioctl.c to add gspca locking requirements Hans Verkuil
2012-05-10 15:35 ` Laurent Pinchart
2012-05-10 17:57   ` Hans de Goede [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=4FAC01A0.2050105@redhat.com \
    --to=hdegoede@redhat.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.