Linux 7.2 is out: why some changes were reverted before the final release

Linus Torvalds announced the final Linux 7.2 kernel on August 16, 2026, UTC. This August 23 report focuses on an important late-stage decision: reverting some changes before the release.

The release message identifies reverts, particularly around DRM scheduling, alongside smaller driver and networking fixes. This is the final release, distinct from the earlier 7.2-rc1 testing stage.

What does a revert mean?

A revert undoes a change. In software development, it can remove a modification that has caused problems while a more suitable solution is prepared.

A release is not only about accumulating features. Preserving a user’s working routine is part of its value as well. This is our interpretation of the engineering decision, rather than a performance measurement.

Removing a change may look like a step backwards in a change list while helping preserve behaviour that existing systems depend on. The amount of new code alone cannot describe that outcome.

Understanding regressions

The Linux 7.2 regression-handling documentation emphasises protecting behaviour that previously worked. In simple terms, a function that stops working after a change needs investigation.

Comparing the before-and-after states helps identify the cause. “The system does not work” provides little detail; naming the device, version and affected function makes the problem easier to examine.

The expected behaviour matters too. A reviewer needs to understand what the system actually did before, rather than relying on a general impression that an update feels worse.

That makes a useful report more specific: describe the operation, identify the change in its result and keep the comparison conditions clear.

A final release and a particular environment

For a team maintaining different machines, a meaningful comparison examines the same workload on the same hardware. It might cover booting, networking and the main application flows.

Clear conditions also help avoid confusing another system change with the effect of a kernel update. This is a general evaluation method, rather than an upgrade we performed.

The release message alone cannot establish the outcome for every device. Evidence from the environment concerned remains important when assessing the practical result.

The wider lesson is that finalisation can involve removing code as well as adding it. A version number identifies a development milestone; stability is assessed through the behaviour that continues to work for users.

Sources

• Linus Torvalds — Linux 7.2 release message, 16 August UTC; reproduced by LWN
• Linux 7.2 documentation — handling regressions