From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: sym53x8xx modprobe error
Date: Sat, 11 Dec 2004 23:38:01 +0000 [thread overview]
Message-ID: <1102808281.7583.2.camel@localhost.localdomain> (raw)
In-Reply-To: <1102801331.7334.9.camel@pluto.connect4less.com>
On Sat, 2004-12-11 at 13:42 -0800, David Christensen wrote:
> While modprobe'ing sym53c8xx, I received the following
> in /var/log/messages:
>
> Dec 11 13:35:31 fs1 wait_for_sysfs[5420]: either wait_for_sysfs (udev
> 039) needs an update to handle the device '/class/spi_transport/0:0:5:0'
> properly (class specific file unavailable) or the sysfs-support of your
> device's driver needs to be fixed,please report to <linux-hotplug-
> devel@lists.sourceforge.net>
I've added this to the class specific file list in udev now.
> Do I need to update something for this?
No, you can safely ignore it. The next udev version will know what file
to expect in this class.
Thanks,
Kay
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
prev parent reply other threads:[~2004-12-11 23:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-11 21:42 sym53x8xx modprobe error David Christensen
2004-12-11 23:38 ` Kay Sievers [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=1102808281.7583.2.camel@localhost.localdomain \
--to=kay.sievers@vrfy.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.