No need, I've manually added the tag when applying this patch for v5.2.
It looks like the patch this one fixes was included in v4.20, however,
I don't think we need to do anything special to accelerate getting
this fix into v5.1 or -stable.