Searched refs:ct_flags (Results 1 – 3 of 3) sorted by relevance
720 !(vport->ct_flags & FC_CT_RFF_ID) || !vport->cfg_restrict_login) { in lpfc_prep_node_fc4type()1676 vport->ct_flags |= FC_CT_RFT_ID; in lpfc_cmpl_ct_cmd_rft_id()1697 vport->ct_flags |= FC_CT_RNN_ID; in lpfc_cmpl_ct_cmd_rnn_id()1718 vport->ct_flags |= FC_CT_RSPN_ID; in lpfc_cmpl_ct_cmd_rspn_id()1739 vport->ct_flags |= FC_CT_RSNN_NN; in lpfc_cmpl_ct_cmd_rsnn_nn()1762 vport->ct_flags |= FC_CT_RSPNI_PNI; in lpfc_cmpl_ct_cmd_rspni_pni()1774 vport->ct_flags = 0; in lpfc_cmpl_ct_cmd_da_id()1794 vport->ct_flags |= FC_CT_RFF_ID; in lpfc_cmpl_ct_cmd_rff_id()2038 vport->ct_flags &= ~FC_CT_RFT_ID; in lpfc_ns_cmd()2072 vport->ct_flags &= ~FC_CT_RNN_ID; in lpfc_ns_cmd()[all …]
629 uint32_t ct_flags; member
166 ct_flags = {177 return parse_flags(statestr, ct_flags)