For focal SRUs we must ensure that all requested patches are also included in all versions newer than focal - this is to avoid any regressions that may occur after upgrades.
Hence I had to look-up the situation of the patches not only in focal (where the four backports apply cleanly), but also on hirsute (5.11), impish (5.13) and jammy (5.15) - and when the commits got upstream accepted. 1) a23816f3cdcb "s390/setup: diag 318: refactor struct" is upstream with v5.10-rc1 and newer 2) 23a60f834406 "s390/kvm: diagnose 0x318 sync and reset" is upstream with v5.10-rc1 and newer 3) 6cbf1e960fa5 "KVM: s390: remove diag318 reset code" is upstream with v5.10-rc6 and newer 4) but 3fd8417f2c72 "KVM: s390: add debug statement for diag 318 CPNC data" was just recently upstream accepted with v5.16-rc1 and newer. Hence first three commits are already in hirsute, impish and jammy, BUT the last one is not, and needs to be applied on hirsute, impish and jammy on top of the work on focal. I'm glad to see that 3fd8417f2c72 can be cleanly cherry-picked from hirsute, impish and jammy. -- 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/1953334 Title: [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel - kernel part Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: New Bug description: Hardware diagnose data (diag 318) of KVM guest kernel cannot be handled. Fix needed to enhance problem determination of guest kernel under KVM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1953334/+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
