From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?UTF-8?B?TWlrYSBQZW50dGlsw6Q=?= Date: Fri, 25 Nov 2005 19:51:37 +0000 Subject: Re: udev-076 and wait_for_sysfs removal Message-Id: <43876B49.2070207@kolumbus.fi> List-Id: References: <43875F86.4030503@kolumbus.fi> In-Reply-To: <43875F86.4030503@kolumbus.fi> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable To: linux-hotplug@vger.kernel.org Kay Sievers wrote: >On Fri, Nov 25, 2005 at 09:01:26PM +0200, Mika Penttil=C3=A4 wrote: > =20 > >>RELEASE-NOTES informs to compensate removal of wait_for_sysfs with : >> ACTION=3D"add", DEVPATH=3D"/devices/*", ENV{PHYSDEVBUS}=3D"?*",=20 >>WAIT_FOR_SYSFS=3D"bus" >> >>Shouldn't class and block devices have this kind of treatment also? >> =20 >> > >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 > > =20 > Indeed, didn't remeber that we delay the physical device events we=20 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=16865&op=CCk _______________________________________________ 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