Comment 3 for bug 1882088

Please ignore my ignorance, but why not bringing this fix separately upstream now?
I think it will not harm the pre SMC-D v2 code (otherwise the backport here would introduce issues in the current 20.04 kernel), and having it upstream now would save some effort to you later and for us it would mean that we have a reliable patch, that is upstream accepted (signed-off) and there would be no fear about further changes to the code.
Therefore we (and I think that's similar for most distributions) rely on upstream accepted patches, for stability, traceability and manageability reasons.
On top it could also be marked upstream for an upstream stable release update and could with that automatically land in kernel 5.4 updates.