ACK: [PATCH 00/14][SRU][Focal] Mpt3sas update to version 35.101.00.00
Kleber Souza
kleber.souza at canonical.com
Thu Dec 3 10:37:51 UTC 2020
On 27.11.20 06:14, Michael Reed wrote:
> This is an SRU request to update the mpt3sas driver in both Focal and Groovy.
> Please refer to the following bug
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899802
>
> The following changes since commit b0daf8c854cf4ff5f11c1aac3e2dbde712dff437:
>
> btrfs: tree-checker: fix incorrect printk format (2020-11-16 11:31:24 -0500)
>
> are available in the Git repository at:
>
> https://git.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/focal mpt3sas_update_focal
>
> for you to fetch changes up to 69d768c2d7aa675cd570c11ce706e6771db54d72:
>
> scsi: mpt3sas: Bump driver version to 35.101.00.00 (2020-11-17 15:29:07 -0600)
Acked-by: Kleber Sacilotto de Souza <kleber.souza at canonical.com>
>
> ----------------------------------------------------------------
> Sreekanth Reddy (14):
> scsi: mpt3sas: Define hba_port structure
> scsi: mpt3sas: Allocate memory for hba_port objects
> scsi: mpt3sas: Rearrange _scsih_mark_responding_sas_device()
> scsi: mpt3sas: Update hba_port's sas_address & phy_mask
> scsi: mpt3sas: Get device objects using sas_address & portID
> scsi: mpt3sas: Rename transport_del_phy_from_an_existing_port()
> scsi: mpt3sas: Get sas_device objects using device's rphy
> scsi: mpt3sas: Update hba_port objects after host reset
> scsi: mpt3sas: Set valid PhysicalPort in SMPPassThrough
> scsi: mpt3sas: Handling HBA vSES device
> scsi: mpt3sas: Add bypass_dirty_port_flag parameter
> scsi: mpt3sas: Handle vSES vphy object during HBA reset
> scsi: mpt3sas: Add module parameter multipath_on_hba
> scsi: mpt3sas: Bump driver version to 35.101.00.00
>
> drivers/scsi/mpt3sas/mpt3sas_base.h | 104 ++-
> drivers/scsi/mpt3sas/mpt3sas_ctl.c | 6 +-
> drivers/scsi/mpt3sas/mpt3sas_scsih.c | 1238 ++++++++++++++++++++++++++----
> drivers/scsi/mpt3sas/mpt3sas_transport.c | 312 ++++++--
> 4 files changed, 1457 insertions(+), 203 deletions(-)
>
More information about the kernel-team
mailing list