linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Justin Tee <justintee8345@gmail.com>
To: linux-scsi@vger.kernel.org
Cc: jsmart2021@gmail.com, justin.tee@broadcom.com,
	Justin Tee <justintee8345@gmail.com>
Subject: [PATCH v2 00/10] Update lpfc to revision 14.4.0.12
Date: Thu,  6 Nov 2025 14:46:29 -0800	[thread overview]
Message-ID: <20251106224639.139176-1-justintee8345@gmail.com> (raw)

Update lpfc to revision 14.4.0.12

This patch set contains updates to log messaging, revision of outdated
comment descriptions, fixes to kref accounting, support for BB credit
recovery in point-to-point mode, and introduction of registering unique
platform name identifiers with fabrics.

The patches were cut against Martin's 6.19/scsi-queue tree.

Justin Tee (10):
  lpfc: Update various NPIV diagnostic log messaging
  lpfc: Revise discovery related function headers and comments
  lpfc: Remove redundant NULL ptr assignment in lpfc_els_free_iocb
  lpfc: Ensure unregistration of rpis for received PLOGIs
  lpfc: Fix leaked ndlp krefs when in point-to-point topology
  lpfc: Modify kref handling for Fabric Controller ndlps
  lpfc: Fix reusing an ndlp that is marked NLP_DROPPED during FLOGI
  lpfc: Allow support for BB credit recovery in point-to-point topology
  lpfc: Add capability to register Platform Name ID to fabric
  lpfc: Update lpfc version to 14.4.0.12

 drivers/scsi/lpfc/lpfc.h           |   4 +-
 drivers/scsi/lpfc/lpfc_ct.c        |  36 +++++
 drivers/scsi/lpfc/lpfc_disc.h      |   3 +-
 drivers/scsi/lpfc/lpfc_els.c       | 249 ++++++++++++++++++++---------
 drivers/scsi/lpfc/lpfc_hbadisc.c   |   6 +-
 drivers/scsi/lpfc/lpfc_hw.h        |  25 ++-
 drivers/scsi/lpfc/lpfc_init.c      |  12 +-
 drivers/scsi/lpfc/lpfc_nportdisc.c |  21 +--
 drivers/scsi/lpfc/lpfc_sli.c       |  79 ++++++++-
 drivers/scsi/lpfc/lpfc_version.h   |   2 +-
 10 files changed, 327 insertions(+), 110 deletions(-)

-- 
2.38.0


             reply	other threads:[~2025-11-06 22:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-06 22:46 Justin Tee [this message]
2025-11-06 22:46 ` [PATCH v2 01/10] lpfc: Update various NPIV diagnostic log messaging Justin Tee
2025-11-06 22:46 ` [PATCH v2 02/10] lpfc: Revise discovery related function headers and comments Justin Tee
2025-11-06 22:46 ` [PATCH v2 03/10] lpfc: Remove redundant NULL ptr assignment in lpfc_els_free_iocb Justin Tee
2025-11-06 22:46 ` [PATCH v2 04/10] lpfc: Ensure unregistration of rpis for received PLOGIs Justin Tee
2025-11-06 22:46 ` [PATCH v2 05/10] lpfc: Fix leaked ndlp krefs when in point-to-point topology Justin Tee
2025-11-06 22:46 ` [PATCH v2 06/10] lpfc: Modify kref handling for Fabric Controller ndlps Justin Tee
2025-11-06 22:46 ` [PATCH v2 07/10] lpfc: Fix reusing an ndlp that is marked NLP_DROPPED during FLOGI Justin Tee
2025-11-06 22:46 ` [PATCH v2 08/10] lpfc: Allow support for BB credit recovery in point-to-point topology Justin Tee
2025-11-06 22:46 ` [PATCH v2 09/10] lpfc: Add capability to register Platform Name ID to fabric Justin Tee
2025-11-06 22:46 ` [PATCH v2 10/10] lpfc: Update lpfc version to 14.4.0.12 Justin Tee
2025-11-08 18:19 ` [PATCH v2 00/10] Update lpfc to revision 14.4.0.12 Martin K. Petersen
2025-11-13  2:46 ` 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=20251106224639.139176-1-justintee8345@gmail.com \
    --to=justintee8345@gmail.com \
    --cc=jsmart2021@gmail.com \
    --cc=justin.tee@broadcom.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;
as well as URLs for NNTP newsgroup(s).