tree 858c77a9aefc2f7b7b2c310b07e243d19a78e148
parent 6f31e42221c7deae4527136ce0dd73990d8bc1d1
author [EMAIL PROTECTED] <[EMAIL PROTECTED]> Tue, 19 Apr 2005 11:57:31 -0700
committer Greg KH <[EMAIL PROTECTED]> Tue, 19 Apr 2005 11:57:31 -0700

[PATCH] add TIMEOUT to firmware_class hotplug event

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 environment of the firmware
requesting event. I will adapt udevd not to wait for anything else, if
it finds a TIMEOUT key.

Signed-off-by: Kay Sievers <[EMAIL PROTECTED]>
Signed-off-by: Greg Kroah-Hartman <[EMAIL PROTECTED]>



 base/firmware_class.c |    3 +++
 1 files changed, 3 insertions(+)

Index: drivers/base/firmware_class.c
===================================================================
--- 71c7e221169721b3a5dfeb4137b2e382090d7814/drivers/base/firmware_class.c  
(mode:100644 sha1:26c9464af80af79583b42c37925194098e4e9dc3)
+++ 858c77a9aefc2f7b7b2c310b07e243d19a78e148/drivers/base/firmware_class.c  
(mode:100644 sha1:97fe13f7f07c85d6fa2d07efd3f04afab932ec46)
@@ -102,6 +102,9 @@
        if (add_hotplug_env_var(envp, num_envp, &i, buffer, buffer_size, &len,
                        "FIRMWARE=%s", fw_priv->fw_id))
                return -ENOMEM;
+       if (add_hotplug_env_var(envp, num_envp, &i, buffer, buffer_size, &len,
+                       "TIMEOUT=%i", loading_timeout))
+               return -ENOMEM;
 
        envp[i] = NULL;
 
-
To unsubscribe from this list: send the line "unsubscribe bk-commits-head" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to