From: Janne Grunau <j@jannau.net>
To: linux-media@vger.kernel.org
Subject: [PATCH 0 of 8] Use usb_interface.dev for v4l2_device_register - try 2
Date: Sun, 29 Mar 2009 16:57:07 +0200 [thread overview]
Message-ID: <20090329145707.GA17855@aniel> (raw)
Hi,
try 2: fixed typo in the cx231xx driver name, the name is set explicitly in
cx2311 not pvrusb2, spltted v4l2_device_register changes and name changes.
the documentation suggest and the current usb driver are using struct device
from the usb_device. As discussed for video_device parent the usb_interface
should be used. This has the advantage that v4l2_device_register creates
meaningfull names, for example "hdpvr usb2-3:1.0" instead of "usb 2-3".
This patch series updates Documentation/video4linux/v4l2-framework.txt and
hopefully all usb drivers uing v4l2_device.
The cx231xx and au0828 drivers are already overriding v4l2_device.name with a
driver name and a device counter. I removed that code since I suspect it was
only added to get meaningful names.
If the current names are preferred just NAK the patches removing that code.
regards,
Janne
reply other threads:[~2009-03-29 14:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20090329145707.GA17855@aniel \
--to=j@jannau.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox