Contributing to Linux
The patch, the mailing list, the maintainer — getting code merged.
The Kernel Community & Maintainer Hierarchy
The Linux kernel is governed not by a company org chart but by a living, trust-based network of maintainers — learning to navigate it is the difference between a patch that lands and one that vanishes.
The Patch Workflow: format-patch, send-email, checkpatch
Master the complete patch lifecycle — from a clean commit to a well-formatted, correctly-threaded email series that maintainers will actually read and merge.
Finding Your First Contribution
Find your foothold in the kernel codebase, craft a real patch, and survive the review gauntlet — from first clone to first Signed-off-by.
Reviewing, Feedback & Patch Versions
Master the complete patch review lifecycle: how to respond, revise, version, and attribute so your patches actually land.
The Release Cycle: Merge Window, -rc, linux-next
The Linux kernel's 10-week heartbeat: how 15,000 commits per cycle travel from a contributor's inbox through maintainer trees, linux-next, and Linus's merge window to the kernel your devices run.
DCO, Signed-off-by & Documentation Contributions
The Developer Certificate of Origin is your cryptographic handshake with the Linux community — a legally meaningful promise that lets millions of contributors collaborate without lawyers in the loop.