Where Rust Kernel Code Lands Before Mainline
New kernel code does not appear in the official release the day it is written. It is first collected in a subsystem maintainer's branch, and for Rust that branch is called rust-next in the rust-for-linux repository. Code sits there, gets tested, and is later pulled into the mainline kernel. Knowing this is why a sample or an interface you read about may exist in one tree and not yet in another.
Questions this Concept answers
- Why can a driver sample exist in one kernel tree and be entirely absent from another?
Rust for Linux
Rust code for Linux does not go straight into the official kernel. It waits in staging branches first: new features queue in one branch, urgent bug fixes in another, and each is handed to the main ke…