Linux 7.2-rc4 Released as Kernel Development Maintains a Steady New Normal

The fourth weekly release candidate of the Linux 7.2 kernel is now available for testing. Following a sequence of development cycles that have been described by Linus Torvalds as a “new normal,” the latest release candidate continues to see a steady volume of code contributions.

A Steady Development Cycle

In the announcement for 7.2-rc4, Linus Torvalds noted that while there was an initial anticipation that development activity might taper off due to the onset of summer vacations, the data indicates that the pace of work remains consistent. Torvalds described the current state of the kernel as not a small rc4, characterized by a fair number of fixes distributed throughout the codebase. The “new normal” mentioned by Torvalds refers to a sustained, slightly higher rate of commits compared to previous development eras. This shift is partially attributed to the ongoing integration of AI and LLM tools in the coding workflow, a trend that has been observed throughout the 7.2 cycle. Despite the increased volume of changes, Torvalds reported that the current status of the kernel appears normal, with the majority of updates consisting of small, incremental fixes.

From Instagram — related to Linus Torvalds, Driver Fixes

Technical Updates and Fixes

The 7.2-rc4 release includes several specific adjustments, though Torvalds noted a lack of particularly notable or “odd” changes. Key areas of activity in the current release candidate include: * Driver Fixes: As with previous versions in the 7.2 cycle, drivers account for a significant portion of the changes. The 7.2-rc4 update includes fixes for the `can/bcm` driver to address issues identified by syzbot, as well as updates to `sashiko` drivers. * GPU and Internal Code: There is a presence of updates regarding AMD GPU code, which primarily involve code movement and comment adjustments rather than significant structural overhauls. * Testing Infrastructure: The kernel’s self-test suite has received additional tests, which are reflected in the current diffs.

Mentorship Session: Trust and the Linux Kernel Development Model

Context of the 7.2 Development Cycle

The progression toward the 7.2 stable release follows the patterns established in the third release candidate (rc3). During the rc3 stage, developers merged updates including Ultra RISC-V support for the default kernel configuration, improved multi-GPU display detection, and critical fixes for Realtek RTL8723BS WiFi adapters. The 7.2 cycle has also highlighted the kernel’s continued support for legacy hardware, including the Sega Dreamcast. In 7.2-rc3, patches were merged to resolve crashes in the Dreamcast Maple mouse driver and to correct the ordering of driver data and device registration for keyboard, mouse, and joystick inputs. Developers maintain that support for such legacy hardware persists as long as there is active interest and contribution from the community. Conversely, features that no longer see practical use—such as i486 support, which was dropped in the 7.1 cycle—are eventually removed.

Context of the 7.2 Development Cycle
Photo: neowin.net

Looking Ahead to Stable Release

The kernel development team is currently tracking toward an August 2026 stable release for Linux 7.2. The release candidate process is a vital phase for public testing and bug reporting, typically spanning approximately 10 release candidates before the final version is finalized. Because the current release candidates have proceeded without major issues or “scary” regressions, there is an expectation that the cycle will remain on schedule. As the community moves through the remainder of the testing phase, participants are encouraged to continue testing and submitting reports to ensure stability before the kernel is deployed in upcoming distribution releases expected later in the autumn.

More on this


Discover more from Archyworldys

Subscribe to get the latest posts sent to your email.