From: Gerd Knorr <kraxel@bytesex.org>
To: Stelian Pop <stelian.pop@fr.alcove.com>,
Marcelo Tosatti <marcelo@conectiva.com.br>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [BK PATCH 2.4] videodev.c oopses in video_exclusive_register
Date: Fri, 15 Mar 2002 20:30:40 +0100 [thread overview]
Message-ID: <20020315203040.A8518@bytesex.org> (raw)
In-Reply-To: <20020315110607.GG13625@come.alcove-fr>
In-Reply-To: <20020315110607.GG13625@come.alcove-fr>
> The recent videodev.c backport doesn't initialise the 'lock' mutex
> which is used in video_exclusive_register.
Oops, good spotting. While checking the 2.5 / 2.4 diff (again ...)
I've noticed I also forgot to delete the old, now unused mutex.
Patch below.
Gerd
==============================[ cut here ]==============================
--- 2.4.19-pre3/drivers/media/video/videodev.c.fix Fri Mar 15 20:03:33 2002
+++ 2.4.19-pre3/drivers/media/video/videodev.c Fri Mar 15 20:04:43 2002
@@ -536,8 +536,6 @@
* %VFL_TYPE_RADIO - A radio card
*/
-static DECLARE_MUTEX(videodev_register_lock);
-
int video_register_device(struct video_device *vfd, int type, int nr)
{
int i=0;
prev parent reply other threads:[~2002-03-15 19:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-15 11:06 [BK PATCH 2.4] videodev.c oopses in video_exclusive_register Stelian Pop
2002-03-15 19:30 ` Gerd Knorr [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=20020315203040.A8518@bytesex.org \
--to=kraxel@bytesex.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=stelian.pop@fr.alcove.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