From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Device Report
Date: Tue, 30 Nov 2004 02:37:25 +0000 [thread overview]
Message-ID: <20041130023724.GA4755@kroah.com> (raw)
In-Reply-To: <1101775719.5124.3.camel@hidlt>
On Tue, Nov 30, 2004 at 01:48:39AM +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>
> ------------------------------------------------------------------------
This has nothing to do with the PAN functionality not working. You can
safely ignore it, it has been fixed in a newer udev version.
thanks,
greg k-h
-------------------------------------------------------
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-11-30 2:37 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
2004-11-30 2:37 ` Greg KH [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=20041130023724.GA4755@kroah.com \
--to=greg@kroah.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 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.