From: dean <dean@sensoray.com>
To: Mauro Carvalho Chehab <mchehab@infradead.org>
Cc: Greg KH <greg@kroah.com>,
v4l-dvb-maintainer@linuxtv.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org, video4linux-list@redhat.com
Subject: Re: [PATCH] USB: add Sensoray 2255 v4l driver
Date: Fri, 16 May 2008 07:53:46 -0700 [thread overview]
Message-ID: <482D9FFA.9030402@sensoray.com> (raw)
In-Reply-To: <20080515235102.756407d3@gaivota>
>Btw, I noticed the lack of Dean's SOB. Is this intentional?
It's not intentional, I can sign off on it. The suggestions look good.
I have a few other questions. First, is Video for Linux version 1 going
to be obsoleted soon? Do the V4L1 compatibility routines still work in
the latest driver? I had problems running the VIVI (virtual video
driver) driver with VideoLan/VLC 0.8.6a-f, but it worked with VLC 9.0
with the new V4L2 interface.
"videodev: "s2255v" has no release callback. Please fix your driver for
proper sysfs support, see http://lwn.net/Articles/36850/"
Should we get rid of the warning message above? It's also been present
in VIVI for quite a few kernel releases.
next prev parent reply other threads:[~2008-05-16 15:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-14 20:59 [PATCH] USB: add Sensoray 2255 v4l driver Greg KH
2008-05-15 1:17 ` [v4l-dvb-maintainer] " Markus Rechberger
2008-05-15 2:41 ` Greg KH
2008-05-15 3:12 ` Trent Piepho
2008-05-15 15:34 ` Dean Anderson
2008-05-15 16:57 ` Markus Rechberger
2008-05-16 2:59 ` Mauro Carvalho Chehab
2008-05-15 11:38 ` Oliver Neukum
2008-05-15 12:03 ` Oliver Neukum
2008-05-15 18:44 ` Greg KH
2008-05-15 19:54 ` Oliver Neukum
2008-05-15 20:10 ` Greg KH
2008-05-15 20:13 ` Oliver Neukum
2008-05-16 2:51 ` Mauro Carvalho Chehab
2008-05-16 6:28 ` Oliver Neukum
2008-05-16 15:57 ` dean
2008-05-16 16:04 ` Oliver Neukum
2008-05-16 18:17 ` Mauro Carvalho Chehab
2008-05-16 14:53 ` dean [this message]
2008-05-16 15:34 ` Mauro Carvalho Chehab
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=482D9FFA.9030402@sensoray.com \
--to=dean@sensoray.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=v4l-dvb-maintainer@linuxtv.org \
--cc=video4linux-list@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).