Public bug reported:

Jeff,

Here are the kernel and cli updates we discussed in email related to
LaunchPad Bug 1855303 to have a complete Broadcom Emulex FC lpfc
12.6.0.x solution.

Please pull these into Ubuntu 20.04.

Thank you
Laurie

Expected that ubuntu is pulling in kernel v5.4  as a base.  These would
go on top of that.

Additional patches recommended:   ( <commitid>   <date>  <patchtitle> )
f16583614222 - Sep 27 2019 - nvme-fc: Sync nvme-fc header to FC-NVME-2
53b2b2f59967 - Sep 27 2019 - nvme-fc and nvmet-fc: sync with FC-NVME-2 header 
changes
44fbf3bb1ac3 - Sep 27 2019 - nvme-fc: Set new cmd set indicator in nvme-fc cmnd 
iu
7db394848ece - Sep 27 2019 - nvme-fc: clarify error messages
bcde5f0fc7d3 - Sep 27 2019 - nvme-fc: ensure association_id is cleared 
regardless of a Disconnect LS
48c9e85b2346 - Oct 14 2019 - nvme: resync include/linux/nvme.h with nvmecli
64fab7290dc3 - Oct 28 2019 - nvme: Fix parsing of ANA log page
863fbae929c7 - Nov 14 2019 - nvme_fc: add module to ops template to allow 
module references
c869e494ef8b - Nov 21 2019 - nvme-fc: fix double-free scenarios on hw queues

----------------------------------------------
- nvme cli rev 1.9 or later must be installed in their system as well, so that 
auto-connect scripts for systemd are installed.
see https://github.com/linux-nvme/nvme-cli

- nvmetcli rev v0.7 or later should be installed in their system as well
see  http://git.infradead.org/users/hch/nvmetcli.git

** Affects: linux (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1856340

Title:
  Update 20.0.4 NVMe Core, NVMe FC Transport and nvme-cli for Broadcom
  Emulex lpfc driver 12.6.0.x dependencies

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856340/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to