Getting Your Patches in Mainline Linux: What Not To Do (& a Few Things You Could Try
summary
Concrete checklist for getting patches merged: use git format-patch/send-email, include a numbered series with a cover letter with vN and changelog, split logical changes into tiny ordered patches, add commit messages and Reviewed-by tags, and re‑post at most weekly while waiting about one week before pinging if a series is unheard. Never copy‑paste or hand‑edit patches, avoid HTML and huge CC lists, and be prepared to refactor upstream pieces or find a mediator if the maintainer does not respond.
AI-written summary · about
chapters (15)
- 0:00Start
- 0:22Opening credits
- 1:26Disclaimer
- 2:40Recurrent themes
- 5:14The Reviewer
- 6:31Motivations
- 8:02The kernel submission workflow
- 9:12What does a patch series look like
- 14:13Use the tools, Luke
- 16:40Using email
- 20:11The maintainer/reviewer workflow
- 24:22Building trust
- 25:03Digression Drive-by patching
- 26:19Becoming a reviewer
- 27:58Be your first reviewer
