NdisMSetInformationComplete function

Note   NDIS 5. x has been deprecated and is superseded by NDIS 6. x. For new NDIS driver development, see Network Drivers Starting with Windows Vista. For information about porting NDIS 5. x drivers to NDIS 6. x, see Porting NDIS 5.x Drivers to NDIS 6.0.

NdisMSetInformationComplete returns the final status of a completed set-information request for which the driver previously returned NDIS_STATUS_PENDING.

Syntax

VOID NdisMSetInformationComplete(
  _In_ NDIS_HANDLE MiniportAdapterHandle,
  _In_ NDIS_STATUS Status
);

Parameters

• MiniportAdapterHandle [in]
  Specifies the handle originally input to MiniportInitialize.

• Status [in]
  Specifies the final status of the immediately preceding request input to MiniportSetInformation.

Return value

None

Remarks

A miniport driver calls NdisMSetInformationComplete after it has carried out the operation orginally requested of its MiniportSetInformation function. This call releases the miniport's ownership of all buffer addresses that were passed to MiniportSetInformation.

NdisMSetInformationComplete causes NDIS to return the original request to the ProtocolRequestComplete function of the driver, if any, that initiated the set-information operation when it called NdisRequest. The NDIS library also can call MiniportSetInformation directly with NDIS-initiated set-information requests, particularly during initialization just after MiniportQueryInformation returns control.

All calls to a driver's MiniportSetInformation function are both synchronous and serialized. That is, NDIS never submits another such request until the miniport driver has completed the preceding request.

For more information about the system-defined OIDs that the MiniportSetInformation function handles, see NDIS Object Identifiers.

A miniport driver must release any spin lock that it is holding before calling NdisMSetInformationComplete.

Requirements

See also

MiniportInitialize

MiniportSetInformation

NDIS_REQUEST

NdisRequest

ProtocolRequestComplete

Send comments about this topic to Microsoft