Comment 4 for bug 1907421

Hi Matthew,
I'm updating the hirsute entry to Fix Committed, since the 5.10 kernel is in hirsute-proposed
and the requested patch is included:
Ubuntu-5.10.0-12.13
v5.10
So we are good with 21.04/hirsute.

And it's great that see that you've managed to get it accepted via upstream stable, since this provides a lot of confidence about the fix that we need for an LTS SRU - and since we have a process in place to pick up stable (upstream) updates, that will find (semi-automatically) it's way into 20.04/focal's Ubuntu kernel 5.4 soon.
So this is highly appreciated.

However, to avoid any regression for people who upgrade from an Ubuntu release n to n+1 (in this case 20.04/focal to 20.10/groovy) one requirement of our SRU process is to get the patches in to the Ubuntu releases/kernels starting from newest to the oldest Ubuntu release the patch needs to be applied to.
Hence me trying to get the patch applied to the groovy master-next tree, based on kernel 5.8, which failed (LP comment #2) (since we knew it's already in 5.10 which is the target for 21.04).
Well, I can retry to apply the patch to groovy master-next, since the groovy master-next tree evolved over time, but I guess it still does not apply - hence me asking for a backport (#2)
Btw. even if 5.8.y ran out of upstream stable support, we still look at the 5.9.y stable updates for inclusion into 5.8. So tagging the fix for stable 5.9.y would be an option, too.