Searched refs:ct_flags (Results 1 – 2 of 2) sorted by relevance
720 !(vport->ct_flags & FC_CT_RFF_ID) || !vport->cfg_restrict_login) { in lpfc_prep_node_fc4type()1686 vport->ct_flags |= FC_CT_RFT_ID; in lpfc_cmpl_ct_cmd_rft_id()1707 vport->ct_flags |= FC_CT_RNN_ID; in lpfc_cmpl_ct_cmd_rnn_id()1728 vport->ct_flags |= FC_CT_RSPN_ID; in lpfc_cmpl_ct_cmd_rspn_id()1749 vport->ct_flags |= FC_CT_RSNN_NN; in lpfc_cmpl_ct_cmd_rsnn_nn()1762 vport->ct_flags = 0; in lpfc_cmpl_ct_cmd_da_id()1782 vport->ct_flags |= FC_CT_RFF_ID; in lpfc_cmpl_ct_cmd_rff_id()2025 vport->ct_flags &= ~FC_CT_RFT_ID; in lpfc_ns_cmd()2059 vport->ct_flags &= ~FC_CT_RNN_ID; in lpfc_ns_cmd()2069 vport->ct_flags &= ~FC_CT_RSPN_ID; in lpfc_ns_cmd()[all …]
604 uint32_t ct_flags; member