Added the SRU template to the bug summary
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Jeff Lane (bladernr)
** Description changed:
Here is a list of patches that need applied to 20.04.4 to bring the
smartpqi up to date with kernel.org.
64fc9015fbeb scsi: smartpqi: Switch to attribute groups
0ca190805784 scsi: smartpqi: Call scsi_done() directly
605ae389ea02 scsi: smartpqi: Update version to 2.1.12-055
80982656b78e scsi: smartpqi: Add 3252-8i PCI id
d4dc6aea93cb scsi: smartpqi: Fix duplicate device nodes for tape changers
987d35605b7e scsi: smartpqi: Fix boot failure during LUN rebuild
28ca6d876c5a scsi: smartpqi: Add extended report physical LUNs
4f3cefc3084d scsi: smartpqi: Avoid failing I/Os for offline devices
be76f90668d8 scsi: smartpqi: Add TEST UNIT READY check for SANITIZE operation
6ce1ddf53252 scsi: smartpqi: Update LUN reset handler
5d1f03e6f49a scsi: smartpqi: Capture controller reason codes
9ee5d6e9ac52 scsi: smartpqi: Add controller handshake during kdump
819225b03dc7 scsi: smartpqi: Update device removal management
5f492a7aa13b scsi: smartpqi: Replace one-element array with flexible-array
member
+
+ [Impact]
+
+ * An explanation of the effects of the bug on users and
+
+ * justification for backporting the fix to the stable release.
+
+ * In addition, it is helpful, but not required, to include an
+ explanation of how the upload fixes this bug.
+
+ [Test Plan]
+
+ * detailed instructions how to reproduce the bug
+
+ * these should allow someone who is not familiar with the affected
+ package to reproduce the bug and verify that the updated package fixes
+ the problem.
+
+ * if other testing is appropriate to perform before landing this update,
+ this should also be described here.
+
+ [Where problems could occur]
+
+ * Think about what the upload changes in the software. Imagine the change is
+ wrong or breaks something else: how would this show up?
+
+ * It is assumed that any SRU candidate patch is well-tested before
+ upload and has a low overall risk of regression, but it's important
+ to make the effort to think about what ''could'' happen in the
+ event of a regression.
+
+ * This must '''never''' be "None" or "Low", or entirely an argument as to why
+ your upload is low risk.
+
+ * This both shows the SRU team that the risks have been considered,
+ and provides guidance to testers in regression-testing the SRU.
+
+ [Other Info]
+
+ * Anything else you think is useful to include
+ * Anticipate questions from users, SRU, +1 maintenance, security teams and
the Technical Board
+ * and address these questions in advance
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1953689
Title:
smartpqi: Update 20.04.4 to latest kernel.org patch level
Status in linux package in Ubuntu:
Incomplete
Bug description:
Here is a list of patches that need applied to 20.04.4 to bring the
smartpqi up to date with kernel.org.
64fc9015fbeb scsi: smartpqi: Switch to attribute groups
0ca190805784 scsi: smartpqi: Call scsi_done() directly
605ae389ea02 scsi: smartpqi: Update version to 2.1.12-055
80982656b78e scsi: smartpqi: Add 3252-8i PCI id
d4dc6aea93cb scsi: smartpqi: Fix duplicate device nodes for tape changers
987d35605b7e scsi: smartpqi: Fix boot failure during LUN rebuild
28ca6d876c5a scsi: smartpqi: Add extended report physical LUNs
4f3cefc3084d scsi: smartpqi: Avoid failing I/Os for offline devices
be76f90668d8 scsi: smartpqi: Add TEST UNIT READY check for SANITIZE operation
6ce1ddf53252 scsi: smartpqi: Update LUN reset handler
5d1f03e6f49a scsi: smartpqi: Capture controller reason codes
9ee5d6e9ac52 scsi: smartpqi: Add controller handshake during kdump
819225b03dc7 scsi: smartpqi: Update device removal management
5f492a7aa13b scsi: smartpqi: Replace one-element array with flexible-array
member
[Impact]
* An explanation of the effects of the bug on users and
* justification for backporting the fix to the stable release.
* In addition, it is helpful, but not required, to include an
explanation of how the upload fixes this bug.
[Test Plan]
* detailed instructions how to reproduce the bug
* these should allow someone who is not familiar with the affected
package to reproduce the bug and verify that the updated package fixes
the problem.
* if other testing is appropriate to perform before landing this update,
this should also be described here.
[Where problems could occur]
* Think about what the upload changes in the software. Imagine the change is
wrong or breaks something else: how would this show up?
* It is assumed that any SRU candidate patch is well-tested before
upload and has a low overall risk of regression, but it's important
to make the effort to think about what ''could'' happen in the
event of a regression.
* This must '''never''' be "None" or "Low", or entirely an argument as to why
your upload is low risk.
* This both shows the SRU team that the risks have been considered,
and provides guidance to testers in regression-testing the SRU.
[Other Info]
* Anything else you think is useful to include
* Anticipate questions from users, SRU, +1 maintenance, security teams and
the Technical Board
* and address these questions in advance
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953689/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
