From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: wait_for_sysfs errors
Date: Thu, 07 Oct 2004 19:15:21 +0000 [thread overview]
Message-ID: <20041007191521.GA22090@kroah.com> (raw)
In-Reply-To: <20041007015347.7fc6588c@Luna.local>
On Thu, Oct 07, 2004 at 02:57:19PM -0400, Jeff wrote:
> On Thu, 7 Oct 2004 10:47:15 -0700
> Greg KH <greg@kroah.com> wrote:
>
> > On Thu, Oct 07, 2004 at 01:53:47AM -0400, Jeff wrote:
> > > You asked for it:
> >
> > Thanks for the info, I'll be adding these devices to the wait_for_sysfs
> > program, so it doesn't spit out these messages for you anymore.
> >
> > greg k-h
> >
>
> Thank you GKH. After reading some posts on the list I'm assuming this
> is for tweaking udev to avoid some of the timing issues that have been
> known to happen (well I know I've had a few but only a sporadic i2c
> device on an older 2.6.5 kernel of late)? Just curious...
Yes, the wait_for_sysfs program, puts all of the logic for how and what
we need to wait for when a device is added to sysfs.
I fixed up the i2c devices, but I'm having a problem with the vcs
devices, sometimes it works for me, and other times it doesn't. Oh
well, back to debugging...
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-07 19:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-07 5:53 wait_for_sysfs errors Jeff
2004-10-07 17:47 ` Greg KH
2004-10-07 18:57 ` Jeff
2004-10-07 19:15 ` Greg KH [this message]
2004-10-10 17:39 ` Sasha Z
2004-10-11 22:39 ` Greg KH
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=20041007191521.GA22090@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).