From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: wait_for_sysfs / udev 38
Date: Fri, 15 Oct 2004 18:30:48 +0000 [thread overview]
Message-ID: <20041015183048.GD14568@kroah.com> (raw)
In-Reply-To: <1097747355.9896.2.camel@localhost>
On Fri, Oct 15, 2004 at 01:06:47PM +0200, Kay Sievers wrote:
> On Fri, Oct 15, 2004 at 11:10:11AM +0200, crazy-b wrote:
> > Hi,
> >
> > > Ah, do these messages go away for a non -mm kernel? If so, I know what
> > > happened...
> >
> > Sorry, I cant test that easily, since I need -mm due to reiser4
>
> I've tested it the other way around then. I get the following with a -mm
> kernel and never had that before:
>
> wait_for_sysfs (udev 038) needs an update to handle the device '/class/usb_host' properly (5)
> wait_for_sysfs (udev 038) needs an update to handle the device '/class/usb' properly (4)
Yes, this is due to a patch in the -mm tree that I need to tell andrew
to drop, but have been busy with other things so far...
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
prev parent reply other threads:[~2004-10-15 18:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-14 9:49 wait_for_sysfs / udev 38 crazy-b
2004-10-14 10:29 ` crazy-b
2004-10-14 23:12 ` Greg KH
2004-10-15 9:10 ` crazy-b
2004-10-15 11:06 ` Kay Sievers
2004-10-15 18:30 ` 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=20041015183048.GD14568@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 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).