From: Kamal Mostafa <kamal@canonical.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
Mauro Carvalho Chehab <mchehab@redhat.com>
Subject: Re: [PATCH] [media] uvcvideo: quirk PROBE_DEF for Dell Studio / OmniVision webcam
Date: Wed, 17 Apr 2013 09:38:43 -0700 [thread overview]
Message-ID: <1366216723.20385.7.camel@fourier> (raw)
In-Reply-To: <3233904.U6nm1cedXx@avalon>
[-- Attachment #1: Type: text/plain, Size: 856 bytes --]
On Wed, 2013-04-17 at 01:05 +0200, Laurent Pinchart wrote:
> Hi Kamal,
>
> On Monday 15 April 2013 12:01:51 Kamal Mostafa wrote:
> > BugLink: https://bugs.launchpad.net/bugs/1168430
> >
> > OminiVision webcam 0x05a9:0x264a (in Dell Studio Hybrid 140g) needs the
> > same UVC_QUIRK_PROBE_DEF as other OmniVision model to be recognized
> > consistently.
> >
> > Signed-off-by: Kamal Mostafa <kamal@canonical.com>
>
> Thank you for the patch.
>
> Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
>
> I've taken the patch in my tree and will submit it upstream for v3.11.
>
> Could you please try to get the full 'lsusb -v -d 05a9:264a' output from the
> bug reporter ?
Thanks Laurent. The requested lsusb dump is now available at
https://launchpadlibrarian.net/137633994/lsusb-omnivision-264a.txt
-Kamal
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-04-17 16:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-15 19:01 [PATCH] [media] uvcvideo: quirk PROBE_DEF for Dell Studio / OmniVision webcam Kamal Mostafa
2013-04-16 23:05 ` Laurent Pinchart
2013-04-17 16:38 ` Kamal Mostafa [this message]
2013-04-21 23:11 ` Laurent Pinchart
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=1366216723.20385.7.camel@fourier \
--to=kamal@canonical.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--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