From: 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 4/4] qla2xxx: enable FPIN notification for NVMe
Date: Mon, 28 Apr 2025 08:36:35 +0200 [thread overview]
Message-ID: <20250428063635.125879-5-hare@kernel.org> (raw)
In-Reply-To: <20250428063635.125879-1-hare@kernel.org>
From: Hannes Reinecke <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 | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/scsi/qla2xxx/qla_isr.c b/drivers/scsi/qla2xxx/qla_isr.c
index fe98c76e9be3..87b5b5e73a6e 100644
--- a/drivers/scsi/qla2xxx/qla_isr.c
+++ b/drivers/scsi/qla2xxx/qla_isr.c
@@ -46,6 +46,7 @@ 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);
+ nvme_fc_fpin_rcv(vha->nvme_local_port, pkt_size, (char *)pkt);
}
const char *const port_state_str[] = {
--
2.35.3
prev parent reply other threads:[~2025-04-28 6:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-28 6:36 [PATCHv3 0/4] nvme-fc: FPIN link integrity handling hare
2025-04-28 6:36 ` [PATCH 1/4] fc_els: use 'union fc_tlv_desc' hare
2025-04-29 0:32 ` Justin Tee
2025-04-29 5:56 ` Hannes Reinecke
2025-04-28 6:36 ` [PATCH 2/4] nvme-fc: marginal path handling hare
2025-04-28 6:36 ` [PATCH 3/4] lpfc: enable FPIN notification for NVMe hare
2025-04-29 0:30 ` Justin Tee
2025-04-29 6:14 ` Hannes Reinecke
2025-04-29 21:28 ` Justin Tee
2025-04-28 6:36 ` hare [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=20250428063635.125879-5-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.