Lines Matching refs:ID
71 left to the application. AF_RXRPC only deals in blobs. Even the operation ID
119 Connection ID
120 Service ID
135 (*) The first four bytes of the request data are the service operation ID.
210 non-zero service ID.
318 MESSAGE ID SRT DATA MEANING
320 RXRPC_USER_CALL_ID sr- User ID App's call specifier
333 This is used to indicate the application's call ID. It's an unsigned long
345 will be returned if there is no call with that user ID.
378 arrived and is awaiting acceptance. No user ID is associated with this,
379 as a user ID must subsequently be assigned by doing an RXRPC_ACCEPT.
384 assign it a user ID. It should be associated with an RXRPC_USER_CALL_ID
385 to indicate the user ID to be assigned. If there is no call to be
387 return error ENODATA. If the user ID is already in use by another call,
540 RXRPC_USER_CALL_ID - specifies the user ID for this call
556 RXRPC_USER_CALL_ID - specifies the user ID for this call
595 .srx_service = VL_SERVICE_ID, /* RxRPC service ID */
623 RXRPC_USER_CALL_ID - specify user ID for this call
635 RXRPC_USER_CALL_ID - specifies the user ID for this call
640 RXRPC_USER_CALL_ID - specifies the user ID for this call
649 RXRPC_USER_CALL_ID - specifies the user ID for this call
659 RXRPC_USER_CALL_ID - specifies the user ID for this call
771 and handling the incoming message, the ID assigned by the kernel utility
807 This is used to accept an incoming call and to assign it a call ID. This
928 serves to anchor the peer data and keeps the connection ID counter.