public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jaya Kumar" <jayakumar.video@gmail.com>
To: "Mauro Carvalho Chehab" <mchehab@infradead.org>
Cc: "Linux and Kernel Video" <video4linux-list@redhat.com>,
	"Simon Evans" <spse@secret.org.uk>,
	linux-usb-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org,
	Dmitri <dmitri@users.sourceforge.net>
Subject: Re: [Fwd: [PATCH 2.6.17-rc4 1/1] usbvideo misc cleanup]
Date: Tue, 23 May 2006 08:14:09 -0400	[thread overview]
Message-ID: <70066d530605230514o7e6c34cfye6465faa6db37547@mail.gmail.com> (raw)
In-Reply-To: <1147903350.30469.16.camel@praia>

On 5/17/06, Mauro Carvalho Chehab <mchehab@infradead.org> wrote:
> Hmm... It seems that those drivers are without any current maintainer.
> At least, from my research, I didn't noticed any patch from a maintainer
> at 2.6 git tree.
>
> Anyway, let's copy both Dmitri and Simon.
>
> I dunno who were the authors for ibmcam and usbvideo.
>
>

I was also wondering if anyone is working on converting usbvideo to
v4l2. There's also a warning message from videodev that is triggered
by usbvideo's template:

videodev does:
357 #if 1 /* needed until all drivers are fixed */
358         if (!vfd->release)
359                 printk(KERN_WARNING "videodev: \"%s\" has no
release callback. "
360                        "Please fix your driver for proper sysfs
support, see "
361                        "http://lwn.net/Articles/36850/\n", vfd->name);
362 #endif

usbvideo does:
958 static const struct video_device usbvideo_template = {
959         .owner =      THIS_MODULE,
960         .type =       VID_TYPE_CAPTURE,
961         .hardware =   VID_HARDWARE_CPIA,
962         .fops =       &usbvideo_fops,
963 };

and so videodev doesn't find .release and complains.

      reply	other threads:[~2006-05-23 12:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-17 22:02 [Fwd: [PATCH 2.6.17-rc4 1/1] usbvideo misc cleanup] Mauro Carvalho Chehab
2006-05-23 12:14 ` Jaya Kumar [this message]

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=70066d530605230514o7e6c34cfye6465faa6db37547@mail.gmail.com \
    --to=jayakumar.video@gmail.com \
    --cc=dmitri@users.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=mchehab@infradead.org \
    --cc=spse@secret.org.uk \
    --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