I have picked those into my branch since they were all in linux-next at
this point for 6.8

On Thu, Dec 14, 2023 at 2:30 AM Chandrakanth Patil <
<email address hidden>> wrote:

> I didn't get you. These below patches will also be included right?
> d0a60e3edaa4 scsi: mpi3mr: Update driver version to 8.5.1.0.0
> 9536af615dc9 scsi: mpi3mr: Support for preallocation of SGL BSG data
> buffers part-3
> fb231d7deffb scsi: mpi3mr: Support for preallocation of SGL BSG data
> buffers part-2
> c432e1675239 scsi: mpi3mr: Support for preallocation of SGL BSG data
> buffers part-1
> 07ac6adda4d3 scsi: mpi3mr: Fetch correct device dev handle for status
> reply descriptor
> f8fb3f39148e scsi: mpi3mr: Block PEL Enable Command on Controller Reset
> and Unrecoverable State
> c01d515687e3 scsi: mpi3mr: Clean up block devices post controller reset
> e5aab848dfdf scsi: mpi3mr: Refresh sdev queue depth after controller reset
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/2045233
>
> Title:
>   [SRU][22.04.04]: mpi3mr driver update
>
> Status in linux package in Ubuntu:
>   Confirmed
> Status in linux source package in Jammy:
>   Opinion
> Status in linux source package in Mantic:
>   Confirmed
> Status in linux source package in Noble:
>   Confirmed
>
> Bug description:
>   [Impact]
>
>   This update has been initiated to incorporate the mpi3mr driver from
>   upstream into the upcoming Ubuntu releases (Ubuntu 22.04.x point
>   releases).
>
>   This has been requested by both Broadcom as the upstream and by one of
>   the larger OEM partners who are going to be selling systems with these
>   storage controllers to customers.  This series of patches includes bug
>   fixes and support for current Broadcom controllers.
>
>   [Fixes]
>   Below are the commit IDs for the latest upstream version (v6.8).
>
>   The 22.04 LTS point kernel already includes the latest mpi3mr driver
>   version 8.0.0.69.0. Therefore, the listed commit IDs below correspond
>   to the subsequent patches.
>
>   The commit IDs listed below are in sequential order from bottom to
>   top, indicating the order for applying the patches.
>
>   linux-next
>   d0a60e3edaa4 scsi: mpi3mr: Update driver version to 8.5.1.0.0
>   9536af615dc9 scsi: mpi3mr: Support for preallocation of SGL BSG data
> buffers part-3
>   fb231d7deffb scsi: mpi3mr: Support for preallocation of SGL BSG data
> buffers part-2
>   c432e1675239 scsi: mpi3mr: Support for preallocation of SGL BSG data
> buffers part-1
>   07ac6adda4d3 scsi: mpi3mr: Fetch correct device dev handle for status
> reply descriptor
>   f8fb3f39148e scsi: mpi3mr: Block PEL Enable Command on Controller Reset
> and Unrecoverable State
>   c01d515687e3 scsi: mpi3mr: Clean up block devices post controller reset
>   e5aab848dfdf scsi: mpi3mr: Refresh sdev queue depth after controller
> reset
>   b4d94164ff32 scsi: mpi3mr: driver version upgrade to 8.5.0.0.50
>   1193a89d2b6d scsi: mpi3mr: Add support for status reply descriptor
>   cb5b60894602 scsi: mpi3mr: Increase maximum number of PHYs to 64 from 32
>   c9260ff28ee5 scsi: mpi3mr: Add PCI checks where SAS5116 diverges from
> SAS4116
>   6fa21eab82be scsi: mpi3mr: Add support for SAS5116 PCI IDs
>
>   Mainline at 6.6/6.7
>   82b2fb52d6ec scsi: mpi3mr: Split off bus_reset function from host_reset
>   9a9068b2afa0 scsi: mpi3mr: Update driver version to 8.5.0.0.0
>   d9a5ab0ea98f scsi: mpi3mr: Enhance handling of devices removed after
> controller reset
>   e7a8648e1ce2 scsi: mpi3mr: WRITE SAME implementation
>   d9adb81e67e9 scsi: mpi3mr: Add support for more than 1MB I/O
>   6f81b1cfdf33 scsi: mpi3mr: Update MPI Headers to version 3.00.28
>   9134211f7bed scsi: mpi3mr: Invoke soft reset upon TSU or event ack time
> out
>
>   [Testing]
>   verify the mpi3mr driver is loaded
>   verify the version string shows 8.5.1.0.0
>
>   [Regression Risk]
>   Low. These patches are contained to the mpi3mr driver code itself and
> are all already accepted upstream.  They cleanly pick into our 6.5 kernel
> tree.
>
>   Broadcom has tested these and the only concern is the kernel warning
>   below in Comment #7
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045233/+subscriptions
>
> Launchpad-Notification-Type: bug
> Launchpad-Bug: distribution=ubuntu; sourcepackage=linux; component=main;
> status=Confirmed; importance=Medium; <email address hidden>;
> Launchpad-Bug: distribution=ubuntu; distroseries=jammy;
> sourcepackage=linux; component=main; status=Opinion; importance=Wishlist;
> assignee=None;
> Launchpad-Bug: distribution=ubuntu; distroseries=mantic;
> sourcepackage=linux; component=main; status=Confirmed; importance=Medium;
> <email address hidden>;
> Launchpad-Bug: distribution=ubuntu; distroseries=noble;
> sourcepackage=linux; component=main; status=Confirmed; importance=Medium;
> <email address hidden>;
> Launchpad-Bug-Information-Type: Public
> Launchpad-Bug-Private: no
> Launchpad-Bug-Security-Vulnerability: no
> Launchpad-Bug-Commenters: bladernr cpatubuntu
> Launchpad-Bug-Reporter: Chandrakanth Patil (cpatubuntu)
> Launchpad-Bug-Modifier: Chandrakanth Patil (cpatubuntu)
> Launchpad-Message-Rationale: Subscriber
> Launchpad-Message-For: bladernr
>
>

-- 
Jeff Lane
Engineering Manager
IHV/OEM Alliances and Server Certification

"Entropy isn't what it used to be."