From: Himanshu Madhani <himanshu.madhani@oracle.com>
To: Justin Tee <justintee8345@gmail.com>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"jsmart2021@gmail.com" <jsmart2021@gmail.com>,
"justin.tee@broadcom.com" <justin.tee@broadcom.com>
Subject: Re: [PATCH 0/9] lpfc: Update lpfc to revision 14.2.0.16
Date: Thu, 2 Nov 2023 15:56:09 +0000 [thread overview]
Message-ID: <2DD6533E-588A-435E-BF2E-C9129249E5E2@oracle.com> (raw)
In-Reply-To: <20231031191224.150862-1-justintee8345@gmail.com>
> On Oct 31, 2023, at 12:12 PM, Justin Tee <justintee8345@gmail.com> wrote:
>
> Update lpfc to revision 14.2.0.16
>
> This patch set contains a user input range check correction, static code
> analyzer fixes, refactoring of clean up code, and logging enhancements.
>
> The patches were cut against Martin's 6.7/scsi-queue tree.
>
> Justin Tee (9):
> lpfc: Correct maximum PCI function value for RAS fw logging
> lpfc: Fix possible file string name overflow when updating firmware
> lpfc: Fix list_entry null check warning in lpfc_cmpl_els_plogi
> lpfc: Eliminate unnecessary relocking in lpfc_check_nlp_post_devloss
> lpfc: Return early in lpfc_poll_eratt when the driver is unloading
> lpfc: Refactor and clean up mailbox command memory free
> lpfc: Enhance driver logging for selected discovery events
> lpfc: Update lpfc version to 14.2.0.16
> lpfc: Copyright updates for 14.2.0.16 patches
>
> drivers/scsi/lpfc/lpfc.h | 1 +
> drivers/scsi/lpfc/lpfc_attr.c | 4 +--
> drivers/scsi/lpfc/lpfc_els.c | 53 ++++++++++++++++++++------------
> drivers/scsi/lpfc/lpfc_hbadisc.c | 2 +-
> drivers/scsi/lpfc/lpfc_init.c | 4 +--
> drivers/scsi/lpfc/lpfc_mbox.c | 6 ++--
> drivers/scsi/lpfc/lpfc_mem.c | 47 ++++++++++++++++------------
> drivers/scsi/lpfc/lpfc_sli.c | 20 +++++++++---
> drivers/scsi/lpfc/lpfc_sli.h | 10 +++---
> drivers/scsi/lpfc/lpfc_version.h | 2 +-
> 10 files changed, 93 insertions(+), 56 deletions(-)
>
> --
> 2.38.0
>
For the series
Reviewed-by: Himanshu Madhani <himanshu.madhani@oracle.com>
--
Himanshu Madhani Oracle Linux Engineering
next prev parent reply other threads:[~2023-11-02 15:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-31 19:12 [PATCH 0/9] lpfc: Update lpfc to revision 14.2.0.16 Justin Tee
2023-10-31 19:12 ` [PATCH 1/9] lpfc: Correct maximum PCI function value for RAS fw logging Justin Tee
2023-10-31 19:12 ` [PATCH 2/9] lpfc: Fix possible file string name overflow when updating firmware Justin Tee
2023-10-31 19:12 ` [PATCH 3/9] lpfc: Fix list_entry null check warning in lpfc_cmpl_els_plogi Justin Tee
2023-10-31 19:12 ` [PATCH 4/9] lpfc: Eliminate unnecessary relocking in lpfc_check_nlp_post_devloss Justin Tee
2023-10-31 19:12 ` [PATCH 5/9] lpfc: Return early in lpfc_poll_eratt when the driver is unloading Justin Tee
2023-10-31 19:12 ` [PATCH 6/9] lpfc: Refactor and clean up mailbox command memory free Justin Tee
2023-10-31 19:12 ` [PATCH 7/9] lpfc: Enhance driver logging for selected discovery events Justin Tee
2023-10-31 19:12 ` [PATCH 8/9] lpfc: Update lpfc version to 14.2.0.16 Justin Tee
2023-10-31 19:12 ` [PATCH 9/9] lpfc: Copyright updates for 14.2.0.16 patches Justin Tee
2023-11-02 15:56 ` Himanshu Madhani [this message]
2023-11-25 2:54 ` [PATCH 0/9] lpfc: Update lpfc to revision 14.2.0.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=2DD6533E-588A-435E-BF2E-C9129249E5E2@oracle.com \
--to=himanshu.madhani@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 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.