From: Hannes Reinecke <hare@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Keith Busch <kbusch@kernel.org>, Sagi Grimberg <sagi@grimberg.me>,
linux-nvme@lists.infradead.org, Hannes Reinecke <hare@kernel.org>
Subject: [PATCH 5/5] qla2xxx: enable FPIN notification for NVMe
Date: Tue, 6 May 2025 17:35:07 +0200 [thread overview]
Message-ID: <20250506153507.83094-6-hare@kernel.org> (raw)
In-Reply-To: <20250506153507.83094-1-hare@kernel.org>
Call 'nvme_fc_fpin_rcv()' to enble FPIN notifications for NVMe.
Signed-off-by: Hannes Reinecke <hare@kernel.org>
---
drivers/scsi/qla2xxx/qla_isr.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/scsi/qla2xxx/qla_isr.c b/drivers/scsi/qla2xxx/qla_isr.c
index fe98c76e9be3..cfe7afc905b4 100644
--- a/drivers/scsi/qla2xxx/qla_isr.c
+++ b/drivers/scsi/qla2xxx/qla_isr.c
@@ -46,6 +46,9 @@ qla27xx_process_purex_fpin(struct scsi_qla_host *vha, struct purex_item *item)
pkt, pkt_size);
fc_host_fpin_rcv(vha->host, pkt_size, (char *)pkt, 0);
+#if (IS_ENABLED(CONFIG_NVME_FC))
+ nvme_fc_fpin_rcv(vha->nvme_local_port, pkt_size, (char *)pkt);
+#endif
}
const char *const port_state_str[] = {
--
2.35.3
prev parent reply other threads:[~2025-05-06 19:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-06 15:35 [PATCHv4 0/5] nvme-fc: FPIN link integrity handling Hannes Reinecke
2025-05-06 15:35 ` [PATCH 1/5] fc_els: use 'union fc_tlv_desc' Hannes Reinecke
2025-05-06 21:51 ` Justin Tee
2025-05-06 15:35 ` [PATCH 2/5] nvme-fc: marginal path handling Hannes Reinecke
2025-05-06 15:35 ` [PATCH 3/5] nvme-fc: nvme_fc_fpin_rcv() callback Hannes Reinecke
2025-05-06 15:35 ` [PATCH 4/5] lpfc: enable FPIN notification for NVMe Hannes Reinecke
2025-05-06 21:50 ` Justin Tee
2025-05-07 5:59 ` Hannes Reinecke
2025-05-07 17:21 ` Justin Tee
2025-05-06 15:35 ` Hannes Reinecke [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250506153507.83094-6-hare@kernel.org \
--to=hare@kernel.org \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox