Avoid an uninitialized value (0) for ha->fc4_type_priority being falsely
interpreted as NVMe priority. Not strictly needed any more after the
previous patch, but makes the fc4_type_priority handling more explicit.
Link: https://lore.kernel.org/r/20191107224839.32417-3-martin.wilck@suse.com
Tested-by: David Bond <dbond@suse.com>
Acked-by: Himanshu Madhani <hmadhani@marvell.com>
Reviewed-by: Bart Van Assche <bvanassche@acm.org>
Signed-off-by: Martin Wilck <mwilck@suse.com>
Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
        u16 n2n_chip_reset;
 } fc_port_t;
 
-#define FC4_PRIORITY_NVME      0
-#define FC4_PRIORITY_FCP       1
+enum {
+       FC4_PRIORITY_NVME = 1,
+       FC4_PRIORITY_FCP  = 2,
+};
 
 #define QLA_FCPORT_SCAN                1
 #define QLA_FCPORT_FOUND       2
 
            ((uint8_t *)vha->hw->nvram)[NVRAM_DUAL_FCP_NVME_FLAG_OFFSET];
 
 
-       return ((data >> 6) & BIT_0);
+       return (data >> 6) & BIT_0 ? FC4_PRIORITY_FCP : FC4_PRIORITY_NVME;
 }