From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev-043
Date: Mon, 08 Nov 2004 21:00:54 +0000 [thread overview]
Message-ID: <1099947654.8789.22.camel@localhost.localdomain> (raw)
In-Reply-To: <200411070449.21228.warpy@gmx.de>
On Sun, 2004-11-07 at 04:49 +0100, Michael Geithe wrote:
> Hi,
>
> only one udev-message found in my logs ;-)
>
> wait_for_sysfs[10013]: either wait_for_sysfs (udev 043) needs an update to
> handle the device '/class/i2c-dev/i2c-2' properly (no bus device link) or the
> sysfs-support of your device's driver needs to be fixed, please report to
> <linux-hotplug-devel@lists.sourceforge.net>
>
class: /sys/class/i2c-dev/i2c-2/
device: /sys/devices/platform/i2c-2
bus: /sys/bus/i2c/devices/2-0290
Hmm, looks like the "device" link should point to:
/sys/devices/platform/i2c-2/2-0290
instead, to match the bus link.
Greg, any idea?
Thanks,
Kay
-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_idU88&alloc_id\x12065&op=click
_______________________________________________
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
next prev parent reply other threads:[~2004-11-08 21:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-07 3:49 udev-043 Michael Geithe
2004-11-08 21:00 ` Kay Sievers [this message]
2004-11-08 21:18 ` udev-043 Greg KH
2004-11-08 22:02 ` udev-043 Kay Sievers
2004-11-08 22:12 ` udev-043 Greg KH
2004-11-08 23:13 ` udev-043 Kay Sievers
2004-11-08 23:51 ` udev-043 Michael Geithe
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=1099947654.8789.22.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.