Searched refs:init_type_reply (Results 1 – 15 of 15) sorted by relevance
168 resp->init_type_reply = attr->init_type_reply; in copy_port_attr_to_resp()
169 props->init_type_reply = resp->attrs.init_type_reply; in pvrdma_query_port()
142 u8 init_type_reply; member
98 port->attr.init_type_reply = RXE_PORT_INIT_TYPE_REPLY; in rxe_init_port_param()
136 props->init_type_reply = 0; in rvt_query_port()
726 rep->init_type_reply = MLX5_GET_PR(hca_vport_context, ctx, in mlx5_query_hca_vport_context()727 init_type_reply); in mlx5_query_hca_vport_context()
636 props->init_type_reply = out_mad->data[41] >> 4; in mlx5_query_mad_ifc_port()
1416 props->init_type_reply = rep->init_type_reply; in mlx5_query_hca_port()
312 __u8 init_type_reply; member
915 u8 init_type_reply; /* bitmask: see ib spec 14.2.5.6 InitTypeReply */ member
4396 u8 init_type_reply[0x4]; member
162 props->init_type_reply = out_mad->data[41] >> 4; in mthca_query_port()
697 u8 init_type_reply; member
703 props->init_type_reply = out_mad->data[41] >> 4; in ib_link_query_port()
249 port_attr->init_type_reply = 0; in bnxt_re_query_port()
Completed in 131 milliseconds