From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: error
Date: Tue, 12 Oct 2004 07:10:01 +0000 [thread overview]
Message-ID: <20041012071001.GA17837@kroah.com> (raw)
In-Reply-To: <1097564518.3807.4.camel@picop180.ups-tlse.fr>
On Tue, Oct 12, 2004 at 09:01:58AM +0200, B. Zhang wrote:
> error: wait_for_sysfs needs an update to handle the device
> '/class/pcmcia_socket/pcmcia_socket1' properly, please report to
> <linux-hotplug-devel@lists.sourceforge.net>
>
> error: wait_for_sysfs needs an update to handle the device
> '/class/pcmcia_socket/pcmcia_socket0' properly, please report to
> <linux-hotplug-devel@lists.sourceforge.net>
>
> error: wait_for_sysfs needs an update to handle the device
> '/class/nvidia/nvidiactl' properly, please report to
> <linux-hotplug-devel@lists.sourceforge.net>
>
> error: wait_for_sysfs needs an update to handle the device
> '/class/ppp/ppp' properly, please report to
> <linux-hotplug-devel@lists.sourceforge.net>
>
> error: wait_for_sysfs needs an update to handle the device
> '/class/net/ppp0' properly, please report to
> <linux-hotplug-devel@lists.sourceforge.net>
With what version of udev is this? The 035 release should fix these
errors.
thanks,
greg k-h
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
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-10-12 7:10 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-12 7:01 error B. Zhang
2004-10-12 7:10 ` Greg KH [this message]
2004-10-12 7:31 ` error B. Zhang
-- strict thread matches above, loose matches on Subject: below --
2019-03-11 3:44 error MAILER-DAEMON
2019-03-11 3:44 error MAILER-DAEMON
2019-03-01 23:57 error Mail Administrator
2017-09-14 9:51 Error MAILER-DAEMON
2017-09-14 9:51 Error MAILER-DAEMON
2017-04-05 11:09 error Prabhod Bangera
[not found] <CAK99BNA_2hwgkLUap_ThOG8drWkP6f74hdW=SNq_DpuNW=j2ew@mail.gmail.com>
[not found] ` <C1F7B566-69F4-4A22-89EA-59B24677DF43@gmail.com>
2016-10-04 17:27 ` error Jeff King
2016-09-22 23:02 error Luciano Schillagi
2016-09-23 4:46 ` error Jeff King
2016-09-07 7:02 Error MAILER-DAEMON
2016-09-07 7:02 Error MAILER-DAEMON
2016-08-26 7:09 Error live-CLLoK8F55wEAvxtiuMwx3w
2016-08-26 7:09 Error live
2016-07-28 6:26 error Returned mail
2016-07-28 6:26 error Returned mail
2014-11-24 16:53 Error Daniel Pavel
2014-08-22 12:43 Error Himanshu Pandey
2014-06-30 10:47 Error Himanshu Pandey
2013-07-10 1:30 Error Chanakya Vattikuti
2013-07-10 15:15 ` Error Konstantin Khomoutov
2008-04-12 17:36 error Paul Amodio
2005-10-20 6:32 error Alexander E. Patrakov
2005-10-20 6:34 ` error Alexander E. Patrakov
2005-02-04 18:19 error avperrotta
2005-02-04 19:59 ` error Michelle Konzack
2005-02-05 1:48 ` error Adrian Bunk
2004-08-09 11:40 Error The Post Office
2004-07-26 23:18 Error jdanield
2004-07-26 14:31 error owner
2004-07-26 14:27 error Mail Delivery Subsystem
[not found] <20040717025309.BEE9E4E71CD@rt1-1.freetelecom.fr>
2004-07-17 2:54 ` Error nobody
2004-07-05 23:52 ERROR stelian.pop-A5NNTvo2L0pl57MIdRCFDg
2004-05-13 7:14 Error kernel
2004-01-28 5:22 Error bob-BJ6v6M5vqdg4Q++5jOxPmw
2003-02-15 19:06 Error Mark K Hannah
[not found] <003a01c2d1cc$c3dc3f40$d301a8c0@pcgijs>
2003-02-11 12:56 ` Error G. Hesen
2003-02-11 16:47 ` Error Alan Cox
2002-09-16 17:56 Error Malcolm Langille
2002-06-21 14:52 error Russell Coker
2002-06-21 15:05 ` error Stephen Smalley
2002-06-21 14:38 error Russell Coker
2002-06-21 14:52 ` error Stephen Smalley
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=20041012071001.GA17837@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.