From: Hans de Goede <hdegoede@redhat.com>
To: Ezequiel Garcia <elezegarcia@gmail.com>
Cc: Mauro Carvalho Chehab <mchehab@redhat.com>,
linux-media@vger.kernel.org, Hans Verkuil <hverkuil@xs4all.nl>
Subject: Re: [PATCH] pwc: Use vb2 queue mutex through a single name
Date: Thu, 09 Aug 2012 13:28:28 +0200 [thread overview]
Message-ID: <50239EDC.9010105@redhat.com> (raw)
In-Reply-To: <1342332033-30250-1-git-send-email-elezegarcia@gmail.com>
Hi,
Thanks for the patch, I've added it to my tree for 3.7:
http://git.linuxtv.org/hgoede/gspca.git/shortlog/refs/heads/media-for_v3.7-wip
Regards,
Hans
On 07/15/2012 08:00 AM, Ezequiel Garcia wrote:
> This lock was being taken using two different names
> (pointers) in the same function.
> Both names refer to the same lock,
> so this wasn't an error; but it looked very strange.
>
> Cc: Hans Verkuil <hverkuil@xs4all.nl>
> Signed-off-by: Ezequiel Garcia <elezegarcia@gmail.com>
> ---
> drivers/media/video/pwc/pwc-if.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/media/video/pwc/pwc-if.c b/drivers/media/video/pwc/pwc-if.c
> index de7c7ba..b5d0729 100644
> --- a/drivers/media/video/pwc/pwc-if.c
> +++ b/drivers/media/video/pwc/pwc-if.c
> @@ -1127,7 +1127,7 @@ static void usb_pwc_disconnect(struct usb_interface *intf)
> v4l2_device_disconnect(&pdev->v4l2_dev);
> video_unregister_device(&pdev->vdev);
> mutex_unlock(&pdev->v4l2_lock);
> - mutex_unlock(pdev->vb_queue.lock);
> + mutex_unlock(&pdev->vb_queue_lock);
>
> #ifdef CONFIG_USB_PWC_INPUT_EVDEV
> if (pdev->button_dev)
>
prev parent reply other threads:[~2012-08-09 11:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-15 6:00 [PATCH] pwc: Use vb2 queue mutex through a single name Ezequiel Garcia
2012-08-09 11:28 ` 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=50239EDC.9010105@redhat.com \
--to=hdegoede@redhat.com \
--cc=elezegarcia@gmail.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@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;
as well as URLs for NNTP newsgroup(s).