Linux 7.2-rc6 sets record for commits as Torvalds calls it biggest RC6 in years
The Linux kernel 7.2-rc6 prepatch release contains 537 non-merge commits, the largest RC6 by volume in years according to Linus Torvalds.
The Linux kernel 7.2-rc6 prepatch landed this week with a commit count that caught even Linus Torvalds off guard. Between 7.2-rc5 and this release, 537 non-merge commits were applied — a figure Torvalds described as making this the biggest RC6 in years by volume. The release arrived on August 3, 2026 according to LWN’s tracking, though Phoronix noted it as August 2, 2026 — a minor timezone artifact that doesn’t affect the substance of what shipped.
The sheer size of the commit queue is unusual for this stage in the cycle. Release candidates typically taper as a kernel version firms up, with RC6 representing a point where the remaining work should be narrowing toward stabilization. Instead, Torvalds called this one “huge” — not a term he deploys casually in release announcements. The distribution of changes breaks down to roughly 60% drivers, 20% networking, and the remaining 20% spread across architecture support, tooling, and filesystems. That’s a fairly typical pattern in absolute terms, just executed at unusual scale.
What this means for the 7.2 release timeline isn’t yet clear. A bloated RC6 can absorb work that might otherwise have pushed into RC7 or RC8, or it can signal that more fixes are still arriving than the maintainers expected at this point. Torvalds has historically preferred to extend the release cycle rather than ship with known regressions, so the next two weeks of commit velocity will determine whether 7.2 proceeds to a standard RC7 or accumulates enough late arrivals to warrant additional release candidates.
The driver dominance in the commit breakdown suggests much of the volume comes from hardware enablement — new device support, quirk fixes for existing silicon, and power management tuning. Networking’s 20% share is substantial for this phase, implying either late-arriving fixes for protocols already in the tree or stabilization work on features that merged earlier in the cycle. The arch/tooling/filesystem remainder is where structural changes tend to hide, and at 20% of 537 commits, that’s enough surface area to contain genuine risk if anything in there touches core paths.
For distributors and downstream maintainers, an oversized RC6 is a signal to pay closer attention than usual to the remaining release candidates. The work landing now hasn’t had the extended bake time that earlier commits received, and the compressed window between RC6 and final release means less opportunity for production workloads to surface edge cases. The kernel’s development process is designed to absorb exactly this kind of variance, but the variance itself is the story this week — a reminder that even a project with three decades of release engineering behind it can still surprise its own maintainer with the sheer weight of what remains to be merged.