NAK: [FOCAL][PULL] Update Broadcom Emulex lpfc driver in 5.4 to 12.6.0.x

[Seth Forshee]

On Thu, Apr 02, 2020 at 04:14:35PM -0400, Jeff Lane wrote:
> BugLink: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855303
> 
> Note, this pull is related to and dependent on
> https://bugs.launchpad.net/bugs/1856340
> 
> which completes the lpfc 12.6.0.x solution from Broadcom Emulex.
> 
> Additionally there are a few patches (outlined in 1855303) that are upstreamed
> in mkp/scsi.git but not yet landed in mainline, so that should be kept in mind.
> 
> This pull should not be accepted without the corresponding pull for 1856340.
> 
> The following changes since commit efceccb46f9f2f601ab1de5a92983bc5d3819879:
> 
>   UBUNTU: SAUCE: mm/page_alloc.c: disable memory reclaim watermark boosting by default (2020-03-30 10:34:11 +0200)
> 
> are available in the Git repository at:
> 
>   https://git.launchpad.net/~bladernr/ubuntu/+source/linux/+git/focal 1855303-lpfc-updates
> 
> for you to fetch changes up to ec8645c361df583b7efc54da7019935b2449161f:
> 
>   scsi: lpfc: add RDF registration and Link Integrity FPIN logging (2020-03-30 13:31:53 -0400)

You have a number of commits here which indicate they were cherry picked
from upstream, but the sha1's don't exist in upstream. These are the
"upstream" sha1's:

 39c4f1a965a9244c3ba60695e8ff8da065ec6ac4
 0ab384a49c548baf132ccef249f78d9c6c506380
 835214f5d5f516a38069bc077c879c7da00d6108
 792f3b90be2aeedf5e076bbe6c5808e693f51c23
 821bc882accaaaf1bbecf5c0ecef659443e3e8cb
 a99c80742af4b58bfd2d16cada8ee73cb9618649
 4cb9e1ddaa145be9ed67b6a7de98ca705a43f998
 6cde2e3e2813f598a39c8e5688480b76b2f40b10
 f6770e7d2329f0b05223fffea9eb821fd2dd038a
 ad6203f975263752e9738a33eacbc92f5bb6f636
 145e5a8a5cbd0c608dfe653c92edb70a580bdbf6
 73ec6d2748dc35db2b32cf3c182a27c4a0837b9b
 df3fe76658ed47617741819a501e2bd2ae446962

If these commits are in linux-next, you need to indicate this in the
"cherry picked from ..." line, like so:

 (cherry picked from commit ... linux-next)

Otherwise you need to indicate what repository they were cherry picked
from, and they should be marked as SAUCE, e.g.:

 (cherry picked from commit ...
  git://...)

Thanks,
Seth