mpt_deregister(9) [centos man page]

MPT_DEREGISTER(9)					       Message-based devices						 MPT_DEREGISTER(9)

NAME

       mpt_deregister - Deregister a protocol drivers resources.

SYNOPSIS

       void mpt_deregister(u8 cb_idx);

ARGUMENTS

       cb_idx
	   previously registered callback handle

DESCRIPTION

       Each protocol-specific driver should call this routine when its module is unloaded.

COPYRIGHT

Kernel Hackers Manual 3.10					     June 2014							 MPT_DEREGISTER(9)

unregister_callback(9r) 												   unregister_callback(9r)

NAME

       unregister_callback - General: Deregisters a configuration callback routine

SYNOPSIS

       int unregister_callback(
	       void (*function) (),
	       int point,
	       int order,
	       ulong argument );

ARGUMENTS

       Specifies the name of the routine that you want to deregister.  You must have previously registered this callback routine by calling regis-
       ter_callback.  Specifies the execution point at which the kernel calls the callback routine previously registered by calling register_call-
       back. The execution point you pass to this argument must match the value you passed to the point argument in the call to register_callback.
       Specifies the order value that you specified in a previous call to register_callback.  Specifies an argument that you want  the	kernel	to
       pass to the callback routine that you previously registered by calling register_callback. The argument you pass to this argument must match
       the value you passed to argument in the call to register_callback. You would pass the integer constant 0L if you passed this in the  previ-
       ous call to register_callback to indicate there is no argument.

DESCRIPTION

       The  unregister_callback  routine deregisters a kernel module's configuration callback routine. The kernel module previously registered its
       routine or routines by calling the register_callback routine. The values you pass to unregister_callback must be the same ones  you  previ-
       ously passed to register_callback to deregister a specific routine. Kernel modules call unregister_callback to deregister the callback rou-
       tine when it is no longer needed.

       A kernel module typically calls unregister_callback when it encounters a fatal error during static or  dynamic  configuration.  The  cfgmgr
       framework  executes  callback routines scheduled to run after single-user mode each time the system goes from multiuser mode to single-user
       mode and back to multiuser mode. You should unregister any callback routines if you do not want this to occur.

NOTES

       The kernel maintains an internal callback list that stores the values you pass to the register_callback	routine.  These  callbacks  remain
       registered until the user removes them.

       The  unregister_callback  routine searches through the callback list for the specified callback routine, the specified point, the specified
       order, and the specified argument and removes that routine from the list.

RETURN VALUES

       Upon successful completion, the unregister_callback routine returns the value ESUCCESS.

       Otherwise, unregister_callback returns the following error constant, defined in /usr/sys/include/sys/errno.h: The value you passed  to  the
       point  argument	is  outside  the minimum and maximum range.  The callback you specified to be removed does not exist in the callback list.
       The callback you specified to be removed does not exist in the callback list.

FILES

SEE ALSO

       Routines: register_callback(9r)

															   unregister_callback(9r)