Upstreaming 201
summary
Practical guidance for getting code accepted into upstream kernels and projects, with concrete commands and checkpoints. Covers using git format-patch and git send-email to create and send patch series, how to write correct Signed-off-by lines and concise changelogs, where to record reviewer responses and MAINTAINERS entries, and using git bisect and CI feedback to close the patchset loop. Emphasizes exact commit-message formatting, proper reply threading, and making only the minimal edits needed for acceptance.
AI-written summary · about
chapters (5)
- 0:00Introduction
- 13:40Key challenges in upstreaming
- 26:10Community collaboration strategies
- 39:31Real-world impact examples
- 50:23Future directions and Q&A
related talks
37mGetting Your Patches in Mainline Linux: What Not To Do (& a Few Things You Could Try
58mHow To Get Your Patch Accepted
34mContributing your first patch to the Qt Project
49mMaking your patch more committable
33mCode review for Open Source
32mHow (Not) to Get the Vendor Driver Merged Upstream
36mNo, It's Never Too Late to Upstream Your Legacy Linux Based Platform
27mBaby Steps to Kernel Hacking