public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Justin Tee <justintee8345@gmail.com>
Cc: linux-scsi@vger.kernel.org, jsmart2021@gmail.com,
	justin.tee@broadcom.com
Subject: Re: [PATCH 0/8] Update lpfc to revision 14.4.0.2
Date: Mon, 06 May 2024 21:58:04 -0400	[thread overview]
Message-ID: <yq17cg6xu24.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20240429221547.6842-1-justintee8345@gmail.com> (Justin Tee's message of "Mon, 29 Apr 2024 15:15:39 -0700")


Justin,

> Update lpfc to revision 14.4.0.2
>
> This patch set contains updates to log messaging, a bug fix related to
> unloading of the driver, clean up patches regarding the abuse of a
> global spinlock, and support for 32 byte CDBs.
>
> The patches were cut against Martin's 6.10/scsi-queue tree.

Applied to 6.10/scsi-staging, thanks!

-- 
Martin K. Petersen	Oracle Linux Engineering

  parent reply	other threads:[~2024-05-07  1:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-29 22:15 [PATCH 0/8] Update lpfc to revision 14.4.0.2 Justin Tee
2024-04-29 22:15 ` [PATCH 1/8] lpfc: Change default logging level for unsolicited CT MIB commands Justin Tee
2024-04-29 22:15 ` [PATCH 2/8] lpfc: Update logging of protection type for T10 DIF I/O Justin Tee
2024-04-29 22:15 ` [PATCH 3/8] lpfc: Clear deferred RSCN processing flag when driver is unloading Justin Tee
2024-04-29 22:15 ` [PATCH 4/8] lpfc: Introduce rrq_list_lock to protect active_rrq_list Justin Tee
2024-04-29 22:15 ` [PATCH 5/8] lpfc: Change lpfc_hba hba_flag member into a bitmask Justin Tee
2024-04-29 22:15 ` [PATCH 6/8] lpfc: Add support for 32 byte CDBs Justin Tee
2024-04-29 22:15 ` [PATCH 7/8] lpfc: Update lpfc version to 14.4.0.2 Justin Tee
2024-04-29 22:15 ` [PATCH 8/8] lpfc: Copyright updates for 14.4.0.2 patches Justin Tee
2024-05-07  1:58 ` Martin K. Petersen [this message]
2024-05-11 18:39 ` [PATCH 0/8] Update lpfc to revision 14.4.0.2 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=yq17cg6xu24.fsf@ca-mkp.ca.oracle.com \
    --to=martin.petersen@oracle.com \
    --cc=jsmart2021@gmail.com \
    --cc=justin.tee@broadcom.com \
    --cc=justintee8345@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