From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Douglas Landgraf <dougsland@gmail.com>,
Gregor Jasny <jasny@vidsoft.de>,
linux-kernel@vger.kernel.org,
video4linux-list <video4linux-list@redhat.com>,
v4l-dvb-maintainer@linuxtv.org, "Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: [v4l-dvb-maintainer] [PATCH] Re: Regression: VIDIOCGMBUF ioctl hangs on bttv driver (2.6.24-rc6)
Date: Mon, 7 Jan 2008 07:43:37 -0200 [thread overview]
Message-ID: <20080107074337.1aabcf07@gaivota> (raw)
In-Reply-To: <20080106232234.GA12783@elte.hu>
On Mon, 7 Jan 2008 00:22:34 +0100
Ingo Molnar <mingo@elte.hu> wrote:
>
> * Douglas Landgraf <dougsland@gmail.com> wrote:
>
> > Hi guys,
> >
> > Gregor, we have converted bttv driver to use vidioc_ioctl2 some
> > days ago. Could you check and create your patch against v4l
> > development tree? Bttv driver does not have anymore bttv_do_ioctl().
>
> this is about the bttv driver in 2.6.24-rc6/(rc7?) hanging. So whatever
> the devel tree does, this fix (if it's a correct fix) needs to be
> commited upstream ASAP.
For sure. I've just sent Linus a pull request for the fix.
On the devel tree, all this code got removed, replaced by a simple function
call at videobuf. So, I don't expect similar issues for 2.6.25.
I've already fixed the patch conflicts at devel branch for v4l/dvb -git tree.
Cheers,
Mauro
prev parent reply other threads:[~2008-01-07 9:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-05 22:33 Regression: VIDIOCGMBUF ioctl hangs on bttv driver (2.6.24-rc6) Gregor Jasny
2008-01-05 23:32 ` Rafael J. Wysocki
2008-01-06 14:15 ` [PATCH] " Gregor Jasny
2008-01-06 15:17 ` Ingo Molnar
2008-01-06 22:53 ` [v4l-dvb-maintainer] " Douglas Landgraf
2008-01-06 22:55 ` Douglas Landgraf
2008-01-06 23:22 ` Ingo Molnar
2008-01-07 2:02 ` Douglas Landgraf
2008-01-07 9:43 ` Mauro Carvalho Chehab [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=20080107074337.1aabcf07@gaivota \
--to=mchehab@infradead.org \
--cc=dougsland@gmail.com \
--cc=jasny@vidsoft.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rjw@sisk.pl \
--cc=v4l-dvb-maintainer@linuxtv.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