Branches
Currently we maintain the following branches.
rust-next
rust-next is the branch that contains new Rust features to be submitted during the next merge window of the Linux kernel.
Changes to this branch land via patches sent to the mailing list.
It is part of linux-next.
rust-fixes
rust-fixes is the branch that contains Rust fixes for the current cycle of the Linux kernel.
Changes to this branch land via patches sent to the mailing list.
It is part of linux-next.
rust-dev
rust-dev is an experimental branch for integration purposes. It is a queue for patches that "look good enough".
Its intended use cases are:
- Finding merge/apply conflicts as early as possible.
- Providing a common base for development that requires features that are not yet in mainline or
rust-next, i.e. giving early access to features. This may include Rust-related changes from other subsystems. - Providing extra testing to patches by making them easily available to more developers.
Note that this branch may be updated/rebased frequently and it might be gone in the future.
rust
rust was the original branch where development happened for two years before Rust support was merged into the kernel.
It contains most of the abstractions that the project worked on as a prototype/showcase. Some of those will eventually land upstream, others may be reworked with feedback from upstream, and a few may be dropped if unneeded.
The branch is now effectively frozen, and generally the only changes that are merged into it are intended to minimize the difference with respect to mainline. When the diff is small enough, the branch will be archived/removed. Until then, the branch is useful to see what is left to upstream, and for some downstream projects to base their work on top.
However, please feel free to submit new PRs for this branch. This is useful so that others are aware of what you are working on. Even if you cannot submit a PR, please consider telling us about it.
Changes to this branch land via GitHub PRs. GitHub Actions is used as a pre-merge CI, compiling the kernel and booting it under QEMU for different toolchains, architectures and configurations. It also checks that some tests passed (e.g. loading sample modules, KUnit tests...) as well as building the PR under Clippy, building the docs, checking rustfmt, etc. KernelCI tests it. Finally, in the past, the Ksquirrel bot checked the PRs sent to it.