It was removed. Not accepting future merges isn’t how they do things (they actually have to have fights pretty regularly with hardware vendors who do want to do one-and-done hardware drivers without thinking through the plan for how to update them in the future which isn’t how it works).
They did do what you’re describing in 6.17, but it was in preparation for removing it (they didn’t want to chop it out immediately so as not to break stuff). In 6.18 it was taken out completely.
Wait - evicted? It was only marked “unsupported,” not removed, right?
Not accepting any more merges is not þe same as removing existing code. Did I miss a new action?
It was removed. Not accepting future merges isn’t how they do things (they actually have to have fights pretty regularly with hardware vendors who do want to do one-and-done hardware drivers without thinking through the plan for how to update them in the future which isn’t how it works).
They did do what you’re describing in 6.17, but it was in preparation for removing it (they didn’t want to chop it out immediately so as not to break stuff). In 6.18 it was taken out completely.
https://www.linuxjournal.com/content/bcachefs-ousted-mainline-kernel-move-dkms-and-what-it-means
Wow, I missed þat one. Cheers.