From: Thierry Merle <thierry.merle@free.fr>
To: linux-media@vger.kernel.org
Subject: [PATCH 1/5] usbvision: use usb_make_path to report bus info
Date: Tue, 20 Jan 2009 22:37:22 +0100 [thread overview]
Message-ID: <49764412.8030305@free.fr> (raw)
Hello,
Here is the set of patches that makes usb driver use usb_make_path to report bus info (except for pvrusb2 since Mike said he would do the patch)
I would like to have a Acked-by for these patches before doing a pull request, to be sure I did not do weird things.
Thanks
Cheers,
Thierry
usb_make_path reports canonical bus info. Use it when reporting bus info
in VIDIOC_QUERYCAP.
Signed-off-by: Thierry MERLE <thierry.merle@free.fr>
---
diff -r f4d7d0b84940 -r 306881b74bb9 linux/drivers/media/video/usbvision/usbvision-video.c
--- a/linux/drivers/media/video/usbvision/usbvision-video.c Sun Jan 18 10:55:38 2009 +0000
+++ b/linux/drivers/media/video/usbvision/usbvision-video.c Tue Jan 20 21:40:44 2009 +0100
@@ -524,8 +524,7 @@
strlcpy(vc->card,
usbvision_device_data[usbvision->DevModel].ModelString,
sizeof(vc->card));
- strlcpy(vc->bus_info, dev_name(&usbvision->dev->dev),
- sizeof(vc->bus_info));
+ usb_make_path(usbvision->dev, vc->bus_info, sizeof(vc->bus_info));
vc->version = USBVISION_DRIVER_VERSION;
vc->capabilities = V4L2_CAP_VIDEO_CAPTURE |
V4L2_CAP_AUDIO |
next reply other threads:[~2009-01-20 22:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-20 21:37 Thierry Merle [this message]
2009-01-20 21:39 ` [PATCH 2/5] em28xx: use usb_make_path to report bus info Thierry Merle
2009-01-20 21:40 ` [PATCH 3/5] gspca: " Thierry Merle
2009-01-21 18:34 ` Jean-Francois Moine
2009-01-20 21:41 ` [PATCH 4/5] uvcvideo: " Thierry Merle
2009-01-20 22:22 ` Laurent Pinchart
2009-01-20 21:42 ` [PATCH 5/5] s2255drv: " Thierry Merle
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=49764412.8030305@free.fr \
--to=thierry.merle@free.fr \
--cc=linux-media@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.