From: Greg KH <greg@kroah.com>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: video4linux-list@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [BUG] cdev_put() race condition
Date: Wed, 17 Dec 2008 12:52:49 -0800 [thread overview]
Message-ID: <20081217205249.GA25893@kroah.com> (raw)
In-Reply-To: <200812172118.29574.hverkuil@xs4all.nl>
On Wed, Dec 17, 2008 at 09:18:29PM +0100, Hans Verkuil wrote:
> On Wednesday 17 December 2008 20:53:29 Greg KH wrote:
> > So why is V4L different than the rest of the kernel in that it wishes to
> > do things differently?
>
> Because it has almost no proper framework to speak of and what little there
> is has been pretty much unchanged since the very beginning.
Ick.
> I'm trying to develop a decent framework that should help support upcoming
> devices and generally make life easier for v4l driver developers.
>
> And I've no idea why we don't just use the device's release() callback for
> this. I'm going to implement this right now :-)
Thanks, that makes oh so much more sense. Let me know when you've
completed it so I can make your cdev change as well.
thanks,
greg k-h
prev parent reply other threads:[~2008-12-17 21:00 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-08 20:56 [BUG] cdev_put() race condition Hans Verkuil
2008-12-16 10:06 ` Hans Verkuil
2008-12-16 20:22 ` Greg KH
2008-12-16 21:00 ` Hans Verkuil
2008-12-16 21:21 ` Greg KH
2008-12-16 23:23 ` Hans Verkuil
2008-12-16 23:30 ` Greg KH
2008-12-17 13:37 ` Hans Verkuil
2008-12-17 14:52 ` Boaz Harrosh
2008-12-17 15:07 ` Hans Verkuil
2008-12-17 16:09 ` Boaz Harrosh
2008-12-17 17:33 ` Hans Verkuil
2008-12-17 18:08 ` Al Viro
2008-12-18 8:12 ` Boaz Harrosh
2008-12-18 8:25 ` Boaz Harrosh
2008-12-17 18:16 ` Greg KH
2008-12-17 19:27 ` Laurent Pinchart
2008-12-17 19:35 ` Greg KH
2008-12-17 19:30 ` Hans Verkuil
2008-12-17 19:38 ` Greg KH
2008-12-17 19:39 ` Hans Verkuil
2008-12-17 19:53 ` Greg KH
2008-12-17 20:18 ` Hans Verkuil
2008-12-17 20:52 ` Greg KH [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=20081217205249.GA25893@kroah.com \
--to=greg@kroah.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=video4linux-list@redhat.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