The patch number 11351 was added via Janne Grunau <j...@jannau.net>
to http://linuxtv.org/hg/v4l-dvb master development tree.
Kernel patches in this development tree may be modified to be backward
compatible with older kernels. Compatibility modifications will be
removed before inclusion into the mainstream Kernel
If anyone has any objections, please let us know by sending a message to:
Linux Media Mailing List <linux-me...@vger.kernel.org>
------
From: Janne Grunau <j...@jannau.net>
v4l: use usb_interface for v4l2_device_register
If usb_interface.dev is used as dev parameter for v4l2_device_register
v4l2_dev.name contains the v4l driver/module name and usb device and
interface instead of a simple "usb x-y".
It also matches the recommendation to set the parent devices for usb
drivers.
Priority: normal
Signed-off-by: Janne Grunau <j...@jannau.net>
---
linux/Documentation/video4linux/v4l2-framework.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff -r 4c7466ea8d64 -r 3d54e7da8077
linux/Documentation/video4linux/v4l2-framework.txt
--- a/linux/Documentation/video4linux/v4l2-framework.txt Wed Apr 01
07:36:31 2009 -0300
+++ b/linux/Documentation/video4linux/v4l2-framework.txt Wed Apr 01
13:30:06 2009 +0200
@@ -90,7 +90,7 @@ NULL, then you *must* setup v4l2_dev->na
NULL, then you *must* setup v4l2_dev->name before calling v4l2_device_register.
The first 'dev' argument is normally the struct device pointer of a pci_dev,
-usb_device or platform_device. It is rare for dev to be NULL, but it happens
+usb_interface or platform_device. It is rare for dev to be NULL, but it happens
with ISA devices or when one device creates multiple PCI devices, thus making
it impossible to associate v4l2_dev with a particular parent.
---
Patch is available at:
http://linuxtv.org/hg/v4l-dvb/rev/3d54e7da807754c18186c67620841cb65fa8b6db
_______________________________________________
linuxtv-commits mailing list
linuxtv-commits@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linuxtv-commits
