From: "Mika Penttilä" <mika.penttila@kolumbus.fi>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev-076 and wait_for_sysfs removal
Date: Fri, 25 Nov 2005 19:51:37 +0000 [thread overview]
Message-ID: <43876B49.2070207@kolumbus.fi> (raw)
In-Reply-To: <43875F86.4030503@kolumbus.fi>
Kay Sievers wrote:
>On Fri, Nov 25, 2005 at 09:01:26PM +0200, Mika Penttilä wrote:
>
>
>>RELEASE-NOTES informs to compensate removal of wait_for_sysfs with :
>> ACTION="add", DEVPATH="/devices/*", ENV{PHYSDEVBUS}="?*",
>>WAIT_FOR_SYSFS="bus"
>>
>>Shouldn't class and block devices have this kind of treatment also?
>>
>>
>
>If a class/ block device has a "device" link, which means it is backed
>by a physical device with a "bus", udevd will delay the execution of the
>class/block event until the event for the "device" has finished. So, this
>should work just by resolving the dependencies, if there isn't something
>going wrong in sysfs.
>
>Kay
>
>
>
Indeed, didn't remeber that we delay the physical device events we
depend on.
Thanks,
Mika
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id\x16865&opÌk
_______________________________________________
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:[~2005-11-25 19:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-25 19:01 udev-076 and wait_for_sysfs removal Mika Penttilä
2005-11-25 19:24 ` Kay Sievers
2005-11-25 19:51 ` Mika Penttilä [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=43876B49.2070207@kolumbus.fi \
--to=mika.penttila@kolumbus.fi \
--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).