Post #1890209
2026-04-25 12:01 UTC
@kernellogger My point about the firehose was that even when testing every .0, it would be the only way for people who use these drivers to chime in before the removal of a driver, and thus potentially avoiding a) work+churn and b) now having an arbitrary series of kernels that won't work for them. IWBNI there was an "early warning system" for driver removals --- though that may invite bike shedding.
I would also argue that it's harder to get a driver back than to not have it removed.
Replies (1)
-
@kernellogger@hachyderm.io 2026-04-25 12:22
@klausman a "git revert cafecafe" is not much work+churn and such reverts (aka reapplying a driver) have been backported to stable series, so the problem can quickly vanish. And harder: yes, but from what I've seen not much harder in most cases. Overall just switching to the latest stable series within two or three weeks after a new mainline release (like Arch, Tumbleweed and Fedora do) should do the trick. Testing mainline -rc1 will be even better, but most likely it will work without that.