From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: James Smart <jsmart2021@gmail.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH 00/11] lpfc: Update lpfc to revision 12.6.0.1
Date: Tue, 05 Nov 2019 23:45:05 -0500 [thread overview]
Message-ID: <yq17e4d3966.fsf@oracle.com> (raw)
In-Reply-To: <20191105005708.7399-1-jsmart2021@gmail.com> (James Smart's message of "Mon, 4 Nov 2019 16:56:57 -0800")
James,
> Update lpfc to revision 12.6.0.1
Applied to 5.5/scsi-queue.
Sad to see yet another driver with AMD workarounds. It really seems like
this should be addressed in the core managed IRQ code.
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2019-11-06 4:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-05 0:56 [PATCH 00/11] lpfc: Update lpfc to revision 12.6.0.1 James Smart
2019-11-05 0:56 ` [PATCH 01/11] lpfc: Fix duplicate unreg_rpi error in port offline flow James Smart
2019-11-05 0:56 ` [PATCH 02/11] lpfc: Fix configuration of BB credit recovery in service parameters James Smart
2019-11-05 0:57 ` [PATCH 03/11] lpfc: Fix kernel crash at lpfc_nvme_info_show during remote port bounce James Smart
2019-11-05 0:57 ` [PATCH 04/11] lpfc: Fix unexpected error messages during RSCN handling James Smart
2019-11-05 0:57 ` [PATCH 05/11] lpfc: Fix dynamic fw log enablement check James Smart
2019-11-05 0:57 ` [PATCH 06/11] lpfc: Sync with FC-NVMe-2 SLER change to require Conf with SLER James Smart
2019-11-05 0:57 ` [PATCH 07/11] lpfc: Clarify FAWNN error message James Smart
2019-11-05 0:57 ` [PATCH 08/11] lpfc: Add registration for CPU Offline/Online events James Smart
2019-11-05 0:57 ` [PATCH 09/11] lpfc: Change default IRQ model on AMD architectures James Smart
2019-11-05 0:57 ` [PATCH 10/11] lpfc: Add enablement of multiple adapter dumps James Smart
2019-11-05 0:57 ` [PATCH 11/11] lpfc: Update lpfc version to 12.6.0.1 James Smart
2019-11-06 4:45 ` Martin K. Petersen [this message]
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=yq17e4d3966.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=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 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.