From: Dave Marquardt <[email protected]>

Add IBMVFC_ASYNC_IS_FPIN_EXT flag bit (0x02) to ibmvfc_async_sub_crq.flags
to distinguish extended FPIN events from standard ones.

Add async_sub_crq field of type ibmvfc_queue to ibmvfc_host to hold the
queue handle for the asynchronous sub-CRQ, alongside the existing crq and
async_crq queues.

Signed-off-by: Dave Marquardt <[email protected]>
---
 drivers/scsi/ibmvscsi/ibmvfc.h | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/drivers/scsi/ibmvscsi/ibmvfc.h b/drivers/scsi/ibmvscsi/ibmvfc.h
index 646aaa01177c..3848fa936e38 100644
--- a/drivers/scsi/ibmvscsi/ibmvfc.h
+++ b/drivers/scsi/ibmvscsi/ibmvfc.h
@@ -773,6 +773,7 @@ struct ibmvfc_async_sub_crq {
        volatile u8 valid;
        u8 flags;
 #define IBMVFC_ASYNC_ID_IS_ASSOC_ID    0x01
+#define IBMVFC_ASYNC_IS_FPIN_EXT       0x02
        u8 link_state;
        u8 fpin_status;
        __be16 event;
@@ -990,6 +991,7 @@ struct ibmvfc_host {
        mempool_t *tgt_pool;
        struct ibmvfc_queue crq;
        struct ibmvfc_queue async_crq;
+       struct ibmvfc_queue async_sub_crq;
        struct ibmvfc_channels scsi_scrqs;
        struct ibmvfc_channels nvme_scrqs;
        struct ibmvfc_npiv_login login_info;

-- 
2.55.0



Reply via email to