Well, you should have looked at the patch before, and simply running checkpatch.pl would have told you about 2000+ codestyle issues which had to be fixed before even getting close to the idea of sending the patch to linux-wireless for upstreaming (or doing a decent review).
The screenshot of that email you present dates long after the dev.openwrt.org trac instance had already been set to read-only mode, so at that point nobody had the power to close that bug ticket, which is sad, because now nobody can get that bountysource award unless they move it to another bug-ticket on bugs.openwrt.org. However, this is unlikely to happend, because the original ticket was quite a collection of maybe or maybe not at all interrelated problems when running rt2x00 on MT7620A/N, with no defined way to repduce "the bug" and hence ever showing that it has been resolved. Nevertheless, if Jamie or anyone in the community would explicitely confirm that a fix you made resolves that infamous tx-queue-issue, I would be on your side. However, you fail to provide any such reference.
By the way, at least up to what I can see, the issue had recently resolved by Stanislaw Gruszka by reverting an earlier commit. The culprit has been:
Author: Stanislaw Gruszka email@example.com
Date: Wed Feb 15 10:25:12 2017 +0100
rt2800: use TXOP_BACKOFF for probe frames
Which degraded performance on MT7620 and apparently also caused the "failed to stop TX queue" issue when running AP mode. Neither me nor you caused that problem, neither me nor you were able to spot it.
I'm sorry for your obvious misery. Please go annoy other people.