From cd84edac7b3affa023c0e3588ab36589c683126b Mon Sep 17 00:00:00 2001
From: Hans Bolinder Removes a driver monitor in much the same way as
@@ -185,7 +185,7 @@
monitors. See The function throws a
This function creates a driver monitor and works in many @@ -449,7 +449,7 @@ eventually lead to one of the following messages being sent:
This message is sent, either immediately if the driver is already loaded and no reloading is @@ -459,7 +459,7 @@ expected to know if reloading is demanded prior to creating a monitor for loading.
This message will be sent if reloading was expected, but the (old) driver made itself @@ -467,7 +467,7 @@ sent if the driver was permanent or statically linked in when trying to create the monitor.
This message will arrive if reloading was
underway, but the
This message will arrive if reloading was underway but the loading for some reason @@ -500,7 +500,7 @@
A driver monitor for unload will eventually result in one of the following messages being sent:
The driver instance monitored is now unloaded. As the unload might have been due to a @@ -508,7 +508,7 @@ again have been loaded when this message arrives.
This message will be sent if unloading was
expected, but while the driver was waiting for
@@ -525,7 +525,7 @@
similar to an
This message will be sent if unloading was
expected, but the driver made itself
@@ -539,7 +539,7 @@
A monitor created as
The load request is registered, but the loading is delayed due to the fact that an earlier instance of the @@ -665,7 +665,7 @@ set. In other words, this return value will always need to be handled!
The load request is registered, but the loading is
delayed due to the fact that an earlier instance of the
@@ -683,7 +683,7 @@
about when the driver is actually loaded. This can
be achieved by using the
When monitoring is requested, and a corresponding
A
Only one
This return value indicates that this call removed the
last
The unload request is registered, but there are still
other