What Happens When a Key Linux Wireless Maintainer Steps Down?
The article outlines Kalle Valo's decade‑long contributions to Linux wireless drivers, his unexpected resignation, the community’s concerns about succession, and the urgent need for new maintainers to ensure the long‑term health of the kernel’s Wi‑Fi subsystem.
Kalle Valo’s Contributions to Linux Wireless
Kalle Valo made his first Linux kernel commit in 2008 for the 2.6 series, submitting the patch spi: omap2_mcspi PIO RX fix. Over more than a decade he became the primary maintainer of the Linux wireless subsystem ( drivers/net/wireless/) and contributed the major Qualcomm Atheros Wi‑Fi drivers:
ATH10K – driver for 802.11ac/ax devices
ATH11K – driver for newer 802.11ax hardware
ATH12K – driver for the latest Wi‑Fi 6/6E chips
Common Atheros tools and firmware handling
His work is used by millions of Linux users worldwide and is integrated into all major distributions.
Resignation Announcement
In a post to the Linux‑wireless mailing list, Valo announced that he will step down from all maintainer roles. He did not give a specific reason for the departure.
He confirmed that Jeff Johnson will continue to maintain the ATH10K, ATH11K and ATH12K drivers, so those drivers will not lose immediate support. However, the broader wireless subsystem ( drivers/net/wireless/) currently has no designated successor.
Valo invited interested developers to contact him or Johannes Berg, a long‑time contributor to the wireless subsystem, to discuss taking over the maintainer responsibilities.
Implications for the Linux Wireless Stack
Short‑term impact : Existing drivers are mature and stable; most users will not notice any regression.
Long‑term risk : Without a new maintainer, future hardware support, bug fixes, and integration with newer kernel versions could stall. The subsystem would lack a clear point of contact for upstream contributions and for coordinating reviews.
Community discussion has highlighted two recurring concerns:
The need for a documented succession plan for critical subsystems.
The importance of designating a “second‑in‑command” to avoid gaps when a sole maintainer departs.
Next Steps for the Community
Developers are encouraged to:
Review the current maintainer list for drivers/net/wireless/ and identify potential candidates.
Engage with Jeff Johnson and Johannes Berg to understand the outstanding technical debt and roadmap.
Contribute patches, documentation, and testing to demonstrate readiness for maintainer responsibilities.
Ensuring a smooth transition will help keep Linux Wi‑Fi drivers compatible with emerging hardware, kernel features, and security requirements.
Reference: https://www.phoronix.com/news/Linux-Wireless-Maintainer-2025
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
Liangxu Linux
Liangxu, a self‑taught IT professional now working as a Linux development engineer at a Fortune 500 multinational, shares extensive Linux knowledge—fundamentals, applications, tools, plus Git, databases, Raspberry Pi, etc. (Reply “Linux” to receive essential resources.)
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.