On linux-next breakage
On linux-next breakage
Posted Dec 15, 2025 10:04 UTC (Mon) by sfr (subscriber, #7761)In reply to: On linux-next breakage by fratti-co
Parent article: Best practices for linux-next
There are already consequences. I use the version of the offending branch that was in the previous day's
linux-next. And keep doing that until it is fixed. I used to just drop it, but occassionally that had roll on effects
to later merges. It is very unusual for such a breakage to last more that a couple of days, and I can't remember
off the top of my head of such a breakage not being fixed before the merge window opens. I do not publish
a linux-next tree with a known build failure in it. That does not mean that there are no unknown build failures
as it is impossible to build for all configs on all architectures.
linux-next. And keep doing that until it is fixed. I used to just drop it, but occassionally that had roll on effects
to later merges. It is very unusual for such a breakage to last more that a couple of days, and I can't remember
off the top of my head of such a breakage not being fixed before the merge window opens. I do not publish
a linux-next tree with a known build failure in it. That does not mean that there are no unknown build failures
as it is impossible to build for all configs on all architectures.
I have even, on occasson, reverted to using an old version of a branch when a failure is reported from other's
testing.