From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Greg KH <gregkh@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: [bootup warning] "driver" has no release callback, .23-rc9
Date: Wed, 03 Oct 2007 06:59:44 -0300 [thread overview]
Message-ID: <1191405584.28201.31.camel@gaivota> (raw)
In-Reply-To: <20071003070816.GA1208@elte.hu>
Hi Ingo,
Em Qua, 2007-10-03 às 09:08 +0200, Ingo Molnar escreveu:
> FYI, there are 7 V4L drivers that produce this (non-fatal) warning:
Those warnings are inoffensive ;) V4L core does provide a generic
release callback. Anyway, we'll take a look on it and fix, to avoid the
warnings.
>
> [ 132.060848] videodev: "vivi" has no release callback. Please fix your
> driver for proper sysfs support, see http://lwn.net/Articles/36850/
>
> [ 132.124436] videodev: "Aztech radio" has no release callback. Please
> fix your driver for proper sysfs support, see
> http://lwn.net/Articles/36850/
>
> [ 135.685993] videodev: "Typhoon Radio" has no release callback. Please
> fix your driver for proper sysfs support, see
> http://lwn.net/Articles/36850/
>
> [ 135.752619] videodev: "TerraTec ActiveRadio" has no release callback.
> Please fix your driver for proper sysfs support, see
> http://lwn.net/Articles/36850/
>
> [ 135.874244] videodev: "RadioTrack radio" has no release callback.
> Please fix your driver for proper sysfs support, see
> http://lwn.net/Articles/36850/
>
> [ 167.937597] videodev: "Zoltrix Radio Plus" has no release callback.
> Please fix your driver for proper sysfs support, see
> http://lwn.net/Articles/36850/
>
> [ 168.021325] videodev: "GemTek radio" has no release callback. Please
> fix your driver for proper sysfs support, see
> http://lwn.net/Articles/36850/
>
> Ingo
--
Cheers,
Mauro
next prev parent reply other threads:[~2007-10-03 9:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-03 7:08 Ingo Molnar
2007-10-03 9:59 ` Mauro Carvalho Chehab [this message]
2007-10-03 10:54 ` Ingo Molnar
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=1191405584.28201.31.camel@gaivota \
--to=mchehab@infradead.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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
all inboxes | Powered by JetHome®