Recent searches
Search options
The two #Bluetooth #regressions[1] recently affecting many people in #Linux mainline and various stable/longterm #kernel series should soon be a thing of the past:
Linus merged fixes into #LinuxKernel 6.12-rc4[2] and Greg queued them for the next stable releases[3].
Wondering what we should learn from this wrt to handling such regressions quickly and ideally even preventing them from hitting stable.
[1] https://lore.kernel.org/all/4e1977ca-6166-4891-965e-34a6f319035f@leemhuis.info/
[2] https://git.kernel.org/torvalds/c/d7f513ae7b108f953cceec8bc96d2e5e83c3ccd0
[3] https://lore.kernel.org/all/2024102100-spongy-etching-0695@gregkh/
@ljs @kernellogger We should of course learn nothing because "stable" backports work as intended, and there's no need to change anything. Also, this is a one-off event, and this never happened in the past and will never happen again.
</sarcasm>
@ljs @kernellogger Did you know -rc kernels were more stable than "stable" kernels?