Thank you. I haven't reported on github for the same reason I didn't report this one there aswell: Odhcp6c issue with my ISP's configuration
I don't have an account and I have reasons (which I'll not be discussing here) to not create one. For odhcp6c, the repository there seems abandoned for the time being and issues and prs go unanswered.
I still think it's better than not reporting at all, more so when I've already provided the cause and possible solution(s) to the aforementioned issues.
As for this issue in question, this is another case where Linux makes it very hard for you to love it. Breaking backwards compatibility for no good reason in a patch kernel version in an obscure commit. Even Microsoft tends to keep "stone age" code around to avoid breaking older, functional programs.
This is a purely cosmetic change intended to help readers find
their way through the implementation.
Too much time spent making their CoC "inclusive", but allowing random contributors to break backwards compatibility for cosmetic reasons, sigh.
I couldn't lzma the kernel's image to the same size as before (around 250 KB more), and I didn't feel like tweaking the compression or recompiling the kernel, and considering there seems to be a 2.4G AP issue at the moment, I'll probably wait this out.
kmod-mdio-netlink is working correctly at the moment, so mdio-tools is a good enough replacement for the time being (adding netlink support to my code requires way too much work, more than what I am willing to put).
The following commands have the same effect as eth-leds off (if someone else needs it):
mdio mdio.0 phy 24 raw 0 0
mdio mdio.0 phy 17 raw 8 0/0x3FFF
mdio mdio.0 phy 17 raw 9 0/0x3FFF
mdio mdio.0 phy 17 raw 10 0/0x3FFF
mdio mdio.0 phy 17 raw 11 0/0x3FFF
mdio mdio.0 phy 17 raw 12 0/0x3FFF
mdio mdio.0 phy 17 raw 13 0/0x3FFF
mdio mdio.0 phy 17 raw 14 0/0x00FF
mdio mdio.0 phy 17 raw 15 0/0xFC00