Pete Batard wrote: > I would really like to get an update on this, because I really can't > understand what the holdup is, or why non related issues seem to be be > shoved into this bug, with the apparent end result of completely > distracting from the matter at hand. [...] > It is *NOT* about tracking whether the 5.x kernel packages have Genet > support. And it is *NOT* about troubleshooting network issues with the > 5.x kernel.
The Debian bug tracking system is quite capable of recording *which* versions an issue is found and fixed in. So it's fine that this bug is marked fixed in 5.x; we still know that it's unfixed in 4.19. Also, there would be no point in enabling this driver in 4.19, only to have people find on upgrade to the next version on Debian that we didn't enable it there. That's why we're concerned with both versions. [...] > I would also greatly appreciate if this could actually be treated with > the level of urgency it requires on account of the following. All "missing hardware support" bugs have severity "important". [...] > - The required patch to *SOLVE* the issue has been provided, so it's not [...] I acknowledge that you have provided a patch, which I appreciate, and I'm sorry you haven't had a specific response to that yet. Generally we want patches that correspond closely to upstream commits. For 5.5 I had to backport these 6 commits: ce69e2162f15 mdio_bus: Add generic mdio_find_bus() 480ded265205 net: bcmgenet: refactor phy mode configuration 6ef31c8bee5b net: bcmgenet: enable automatic phy discovery 99c6b06a37d4 net: bcmgenet: Initial bcmgenet ACPI support 26bd9cc64faf net: bcmgenet: Fetch MAC address from the adapter ae200c26b32b net: bcmgenet: reduce severity of missing clock warnings Can you please provide separate backports of these, instead of a single patch where it's hard to see what changed? Ben. -- Ben Hutchings - Debian developer, member of kernel, installer and LTS teams
signature.asc
Description: This is a digitally signed message part
