Re: [PATCH] add TIMEOUT to firmware_class hotplug event

2005-03-17 Thread Greg KH
On Thu, Mar 17, 2005 at 03:34:31AM +0100, Kay Sievers wrote: > On Tue, 2005-03-15 at 09:25 +0100, Hannes Reinecke wrote: > > The current implementation of the firmware class breaks a fundamental > > assumption in udevd: that the physical device can be initialised fully > > prior to executing the ne

Re: [PATCH] add TIMEOUT to firmware_class hotplug event

2005-03-17 Thread Greg KH
On Thu, Mar 17, 2005 at 12:07:55PM +0100, Kay Sievers wrote: > On Wed, 2005-03-16 at 21:46 -0800, Greg KH wrote: > > On Thu, Mar 17, 2005 at 03:34:31AM +0100, Kay Sievers wrote: > > > On Tue, 2005-03-15 at 09:25 +0100, Hannes Reinecke wrote: > > > > The current implementation of the firmware class

Re: [PATCH] add TIMEOUT to firmware_class hotplug event

2005-03-17 Thread Kay Sievers
On Wed, 2005-03-16 at 21:46 -0800, Greg KH wrote: > On Thu, Mar 17, 2005 at 03:34:31AM +0100, Kay Sievers wrote: > > On Tue, 2005-03-15 at 09:25 +0100, Hannes Reinecke wrote: > > > The current implementation of the firmware class breaks a fundamental > > > assumption in udevd: that the physical dev

Re: [PATCH] add TIMEOUT to firmware_class hotplug event

2005-03-16 Thread Greg KH
On Thu, Mar 17, 2005 at 03:34:31AM +0100, Kay Sievers wrote: > On Tue, 2005-03-15 at 09:25 +0100, Hannes Reinecke wrote: > > The current implementation of the firmware class breaks a fundamental > > assumption in udevd: that the physical device can be initialised fully > > prior to executing the ne

[PATCH] add TIMEOUT to firmware_class hotplug event

2005-03-16 Thread Kay Sievers
On Tue, 2005-03-15 at 09:25 +0100, Hannes Reinecke wrote: > The current implementation of the firmware class breaks a fundamental > assumption in udevd: that the physical device can be initialised fully > prior to executing the next event for that device. Here we add a TIMEOUT value to the hotplug