From: "Michal Čihař" <michal@cihar.com>
To: linux-hotplug@vger.kernel.org
Subject: DVB & wait_for_sysfs
Date: Sun, 31 Oct 2004 15:00:58 +0000 [thread overview]
Message-ID: <200410311600.58291.michal@cihar.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1413 bytes --]
Hi all
I just found that wait_for_sysfs complains about DVB devices:
wait_for_sysfs[2579]: either wait_for_sysfs (udev 040) needs an update to
handle the device '/class/dvb/dvb0.demux0' properly (no device symlink) or
the sysfs-support of your device's driver needs to be fixed, please report to
<linux-hotplug-devel@lists.sourceforge.net>
wait_for_sysfs[2581]: either wait_for_sysfs (udev 040) needs an update to
handle the device '/class/dvb/dvb0.dvr0' properly (no device symlink) or the
sysfs-support of your device's driver needs to be fixed, please report to
<linux-hotplug-devel@lists.sourceforge.net>
wait_for_sysfs[2583]: either wait_for_sysfs (udev 040) needs an update to
handle the device '/class/dvb/dvb0.net0' properly (no device symlink) or the
sysfs-support of your device's driver needs to be fixed, please report to
<linux-hotplug-devel@lists.sourceforge.net>
wait_for_sysfs[2622]: either wait_for_sysfs (udev 040) needs an update to
handle the device '/class/dvb/dvb0.frontend0' properly (no device symlink) or
the sysfs-support of your device's driver needs to be fixed, please report to
<linux-hotplug-devel@lists.sourceforge.net>
Sorry if this is duplicate report, I write this offline and so I can't check
archives. I'm running 2.6.10-rc1 kernel.
I'm not on the list, so please cc me on reply, thanks.
--
Michal Čihař | http://cihar.com
[-- Attachment #2: Type: application/pgp-signature, Size: 194 bytes --]
next reply other threads:[~2004-10-31 15:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-31 15:00 Michal Čihař [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-11-01 23:53 DVB & wait_for_sysfs Kay Sievers
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=200410311600.58291.michal@cihar.com \
--to=michal@cihar.com \
--cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).