From: James Smart <jsmart2021@gmail.com>
To: linux-scsi@vger.kernel.org
Cc: James Smart <jsmart2021@gmail.com>
Subject: [PATCH 00/12] lpfc: Update lpfc to revision 14.2.0.3
Date: Thu, 5 May 2022 20:55:07 -0700 [thread overview]
Message-ID: <20220506035519.50908-1-jsmart2021@gmail.com> (raw)
Update lpfc to revision 14.2.0.3
This patch set contains fixes in several different areas including
ref counting areas, oops, I/O length failures, etc.
The patches were cut against Martin's 5.19/scsi-queue tree
James Smart (12):
lpfc: Fix element offset in __lpfc_sli_release_iocbq_s4()
lpfc: Fill in missing ndlp kref puts in error paths
lpfc: Fix ndlp put following a LOGO completion
lpfc: Inhibit aborts if external loopback plug is inserted
lpfc: Fix dmabuf ptr assignment in lpfc_ct_reject_event
lpfc: Use list_for_each_entry_safe on fc_nodes list in
rscn_recovery_check
lpfc: Decrement outstanding gidft_inp counter if lpfc_err_lost_link
lpfc: Change VMID registration to be based on fabric parameters
lpfc: Rework FDMI initialization after link up
lpfc: Alter FPIN stat accounting logic
lpfc: Use sg_dma_address and sg_dma_len macros for NVMe I/O
lpfc: Update lpfc version to 14.2.0.3
drivers/scsi/lpfc/lpfc.h | 4 +
drivers/scsi/lpfc/lpfc_crtn.h | 1 +
drivers/scsi/lpfc/lpfc_ct.c | 114 ++++++++++++++++++++++++++---
drivers/scsi/lpfc/lpfc_els.c | 79 +++++++++-----------
drivers/scsi/lpfc/lpfc_hbadisc.c | 21 ++++--
drivers/scsi/lpfc/lpfc_init.c | 65 ++++++++--------
drivers/scsi/lpfc/lpfc_nportdisc.c | 15 +++-
drivers/scsi/lpfc/lpfc_nvme.c | 9 ++-
drivers/scsi/lpfc/lpfc_scsi.c | 17 +++--
drivers/scsi/lpfc/lpfc_sli.c | 35 ++++-----
drivers/scsi/lpfc/lpfc_version.h | 2 +-
11 files changed, 242 insertions(+), 120 deletions(-)
--
2.26.2
next reply other threads:[~2022-05-06 3:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-06 3:55 James Smart [this message]
2022-05-06 3:55 ` [PATCH 01/12] lpfc: Fix element offset in __lpfc_sli_release_iocbq_s4() James Smart
2022-05-06 3:55 ` [PATCH 02/12] lpfc: Fill in missing ndlp kref puts in error paths James Smart
2022-05-06 3:55 ` [PATCH 03/12] lpfc: Fix ndlp put following a LOGO completion James Smart
2022-05-06 3:55 ` [PATCH 04/12] lpfc: Inhibit aborts if external loopback plug is inserted James Smart
2022-05-06 3:55 ` [PATCH 05/12] lpfc: Fix dmabuf ptr assignment in lpfc_ct_reject_event James Smart
2022-05-06 3:55 ` [PATCH 06/12] lpfc: Use list_for_each_entry_safe on fc_nodes list in rscn_recovery_check James Smart
2022-05-06 3:55 ` [PATCH 07/12] lpfc: Decrement outstanding gidft_inp counter if lpfc_err_lost_link James Smart
2022-05-06 3:55 ` [PATCH 08/12] lpfc: Change VMID registration to be based on fabric parameters James Smart
2022-05-06 3:55 ` [PATCH 09/12] lpfc: Rework FDMI initialization after link up James Smart
2022-05-06 3:55 ` [PATCH 10/12] lpfc: Alter FPIN stat accounting logic James Smart
2022-05-06 3:55 ` [PATCH 11/12] lpfc: Use sg_dma_address and sg_dma_len macros for NVMe I/O James Smart
2022-05-06 16:41 ` Jerry Snitselaar
2022-05-06 3:55 ` [PATCH 12/12] lpfc: Update lpfc version to 14.2.0.3 James Smart
2022-05-11 2:11 ` [PATCH 00/12] lpfc: Update lpfc to revision 14.2.0.3 Martin K. Petersen
2022-05-17 2:16 ` Martin K. Petersen
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=20220506035519.50908-1-jsmart2021@gmail.com \
--to=jsmart2021@gmail.com \
--cc=linux-scsi@vger.kernel.org \
/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