From: Greg KH <gregkh@linuxfoundation.org>
To: James Smart <jsmart2021@gmail.com>
Cc: stable@vger.kernel.org, justintee8345@gmail.com,
martin.petersen@oracle.com
Subject: Re: [PATCH v2 0/6] lpfc: LTS 5.15 update to correct path split changes
Date: Mon, 31 Oct 2022 08:26:45 +0100 [thread overview]
Message-ID: <Y194tUNlsWa+MpYU@kroah.com> (raw)
In-Reply-To: <20221028210827.23149-1-jsmart2021@gmail.com>
On Fri, Oct 28, 2022 at 02:08:21PM -0700, James Smart wrote:
> An issue was identified with lpfc in the LTS 5.15 kernel. There is an
> FLOGI failure which prevents FC link bringup.
>
> In the past several kernel releases, we have been reworking areas of
> the driver to fix issues in the broader design rather than continuing
> to create a patchwork on an issue-by-issue basis. This means there are
> a lot of inter-related patches.
>
> In this case, it appears that a portion of the "path split" rework was
> pulled into 5.15, and the portion that wasn't picked up introduced
> the error.
>
> This patch set reverts the patches for the partial pull in.
All now queued up, thanks.
greg k-h
next prev parent reply other threads:[~2022-10-31 7:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-28 21:08 [PATCH v2 0/6] lpfc: LTS 5.15 update to correct path split changes James Smart
2022-10-28 21:08 ` [PATCH v2 1/6] Revert "scsi: lpfc: Resolve some cleanup issues following SLI path refactoring" James Smart
2022-10-28 21:08 ` [PATCH v2 2/6] Revert "scsi: lpfc: Fix element offset in __lpfc_sli_release_iocbq_s4()" James Smart
2022-10-28 21:08 ` [PATCH v2 3/6] Revert "scsi: lpfc: Fix locking for lpfc_sli_iocbq_lookup()" James Smart
2022-10-28 21:08 ` [PATCH v2 4/6] Revert "scsi: lpfc: SLI path split: Refactor SCSI paths" James Smart
2022-10-28 21:08 ` [PATCH v2 5/6] Revert "scsi: lpfc: SLI path split: Refactor fast and slow paths to native SLI4" James Smart
2022-10-28 21:08 ` [PATCH v2 6/6] Revert "scsi: lpfc: SLI path split: Refactor lpfc_iocbq" James Smart
2022-10-31 7:26 ` Greg KH [this message]
2022-10-31 14:02 ` [PATCH v2 0/6] lpfc: LTS 5.15 update to correct path split changes James Smart
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=Y194tUNlsWa+MpYU@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=jsmart2021@gmail.com \
--cc=justintee8345@gmail.com \
--cc=martin.petersen@oracle.com \
--cc=stable@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.