Lines Matching full:callbacks

76 The arguments passed into the callbacks when they are invoked, include:
126 register notify and finalize callbacks for certain events. These events are
132 notify callbacks for that event have the opportunity of blocking such events.
154 Finalize callbacks can be registered for all events including events that
164 callbacks  registered against the exported minor nodes.
168 with respect to these callbacks:
178 An example of an event that can be blocked and for which notify callbacks may
195 Layered drivers may register one or both of these callbacks (that is, only
200 with both callbacks set to \fBNULL\fR.
206 \fBLDI\fR handle is open. If an \fBLDI\fR handle against which the callbacks
207 are registered is closed, the corresponding finalize and notify callbacks is
235 has been closed, no corresponding callbacks is invoked.
249 The notify and finalize callbacks are not automatically unregistered even if
251 the layered driver to unregister these callbacks when they are not required. It
255 corresponding callbacks have not been unregistered.
347 \fBExample 1 \fRRegistration and Callbacks for the OFFLINE Event
456 \fBExample 2 \fRRegistration and Callbacks for the DEGRADE Event
476         /* no notify callbacks allowed for degrade events */