Leo Prikler writes:

> It appears that back in the day they were reverted with
> 918a099e7422fe8ad3464dc5a1b4f60843297742 before a staging merge on
> February 1st.  If nothing else happened on staging since, someone will
> need to revert the revert or apply the patches themselves once more.

These patches were pushed to 'staging-next' branch because 'staging'
branch was forzen at that time. So maybe this is a mistake that we
forget to pick them back to the 'staging'? Should I open a issue to
cherrypick that patches?

-- 
Retrieve my PGP public key:

  gpg --recv-keys D47A9C8B2AE3905B563D9135BE42B352A9F6821F

Zihao