From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: wait_for_sysfs needs an update to handle the device '/class/drm/radeon' properly
Date: Fri, 15 Oct 2004 11:10:58 +0000 [thread overview]
Message-ID: <20041015111058.GB5024@vrfy.org> (raw)
In-Reply-To: <1097699112.416d8f28dae2b@mail.utca.hu>
On Fri, Oct 15, 2004 at 11:50:08AM +0200, Peter Van Eynde wrote:
> Got this message on my IBM R40.
>
> If you need more information, just ask.
This should not happen anymore since udev v035 (4 days ago).
Thanks,
Kay
-------------------------------------------------------
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-15 11:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-13 20:25 wait_for_sysfs needs an update to handle the device properly Csan
2004-10-14 0:01 ` Greg KH
2004-10-15 9:50 ` wait_for_sysfs needs an update to handle the device '/class/drm/radeon' properly Peter Van Eynde
2004-10-15 11:10 ` Kay Sievers [this message]
2004-10-17 7:34 ` wait_for_sysfs needs an update to handle the device '/class/net/wlan0' properly Ralf Hildebrandt
2004-10-17 11:10 ` Kay Sievers
2004-10-29 0:45 ` wait_for_sysfs needs an update to handle the device '/class/capi/capi' Marc Schiffbauer
2004-10-29 1:05 ` wait_for_sysfs needs an update to handle the device '/class/firmware/0000:01:0d.0' Marc Schiffbauer
2004-10-30 3:17 ` Kay Sievers
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=20041015111058.GB5024@vrfy.org \
--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).