LEDE folks have started to dump their patches on kernel mailing lists, but they don't seem to be mainline-able as is and the submitter is loathe to rework them:
Perhaps there is more context, but from a narrow read: the linked email states a need, contains a patch that solves the problem, and offers to solve it another way if needed... that seems pretty mature?
The text literally says:
> I am not sure if this is the best way to remove the quirks from the build. Let me know if you prefer a different way of solving this.
I can speak from experience that some of the LEDE/OpenWRT core people are fairly toxic at times. John Crispin in particular is known to go autistic on you if you top-post on one of his mailing lists instead of bottom-post. He's a real laces-out kinda guy.
"obviously i am interested to get this upstream with the least amount of effort. I am quite aware though that some patches will need an overhaul to be applicable for upstream. its not really my call if it is enough to make this an enable patch and review the quirks enabled by it or if the code needs to be moved."
Upstreaming patches into the kernel requires that you're willing to spend time to rework them so that the result is maintainable. Saying from the start that you only want to do the least amount of work possible isn't helpful.
The majority of OpenWRT/LEDE patches are gross hacks that need a major rework or a completely different approach.
This is not the first patch of that kind.
The text literally says:
> I am not sure if this is the best way to remove the quirks from the build. Let me know if you prefer a different way of solving this.