From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: Device Report
Date: Tue, 30 Nov 2004 02:34:23 +0000 [thread overview]
Message-ID: <1101782064.3021.9.camel@localhost.localdomain> (raw)
In-Reply-To: <1101775719.5124.3.camel@hidlt>
On Tue, 2004-11-30 at 01:48 +0100, Ugo Viti wrote:
> HI,
>
> i'm trying to use the PAN functionality of BlueZ Stack (via USB Dongle).
>
> When the remote bluetooth device connect to my NAP machine i receive in
> the message logs the following entry:
>
> -----------------------------------------------------------------------
> Nov 30 01:44:40 hidlt wait_for_sysfs[5093]: either wait_for_sysfs (udev
> 039) needs an update to handle the device '/class/net/bnep0' 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>
> ------------------------------------------------------------------------
>
> I'm running Fedora Core 3 updated today.
>
> udev version: udev-039-10.FC3.2
That's already fixed in a later version of udev, not to print this.
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
next prev parent reply other threads:[~2004-11-30 2:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-30 0:48 Device Report Ugo Viti
2004-11-30 2:34 ` Kay Sievers [this message]
2004-11-30 2:37 ` Greg KH
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=1101782064.3021.9.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 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).