From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: wait_for_syfs errors
Date: Fri, 22 Oct 2004 23:23:52 +0000 [thread overview]
Message-ID: <20041022232351.GA27599@kroah.com> (raw)
In-Reply-To: <cdb29eb1041022131243fcee79@mail.gmail.com>
On Fri, Oct 22, 2004 at 10:39:07PM +0200, Kay Sievers wrote:
> On Fri, Oct 22, 2004 at 10:22:29PM +0200, Marcel Paulekuhn wrote:
> > Hm yeah, I am, 2.6.9-mm1.
> >
> > So there's no other way to fix this than changing kernel? Because I
> > want to keep reiser4-support.
> >
> >
> > On Fri, 22 Oct 2004 22:17:46 +0200, Kay Sievers <kay.sievers@vrfy.org> wrote:
> > >
> > > You are running a -mm kernel, right? There is a bug in there, that
> > > causes this.
>
> The message is not critical. It just means, that you get (useless) hotplug
> events for the class itself which should not happen. This will hopefully
> fixed soon in the -mm tree and will go away.
Actually I just commited that change to the main kernel tree, so we need
to fix this up in wait_for_sysfs before we start to get a lot of people
complaining :)
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-22 23:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-22 20:12 wait_for_syfs errors Marcel Paulekuhn
2004-10-22 20:17 ` Kay Sievers
2004-10-22 20:22 ` Marcel Paulekuhn
2004-10-22 20:39 ` Kay Sievers
2004-10-22 23:23 ` Greg KH [this message]
2004-10-23 1:59 ` 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=20041022232351.GA27599@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).