Code Review Training for Kernel Patch Reviewers
Talkat Embedded Linux Conference + OpenIoT Summit North America 2017 · on Wednesday, 2017-02-22· at 10:30· Broadway III/IV·
summary
Describes hands-on rules for maintaining vendor kernel trees: how to migrate a 4.4→4.9 rebase, enforce a commit-prefix discipline (upstream/fromlist/vendor/RFC), and avoid one-line “revert me” commits that break migrations. Covers tools and checks used: checkpatch output, static/security scanners, Gerrit workflow and Yocto build failures; gives concrete rejection reasons (missing testable behavior, leaked IP, incorrect locking) and when to escalate or require follow-ups. Useful if responsible for long-term integration and backports.
AI-written summary · about
chapters (12)
- 0:00INTRODUCTION
- 0:59COURSE OUTLINE
- 3:18COURSE GOALS
- 7:31HIGH LEVEL POLICIES
- 8:27COMMIT PREFIX CONVENTIONS
- 11:46EXAMPLES HERE
- 17:09STRUCTURE OF CODE REVIEWS
- 18:15SUPPORTABILITY
- 29:08CORRECTNESS
- 36:26A WORD ABOUT CHECKPATCH.PL
- 44:16DETAILS OF A GOOD CODE REVIEW
- 48:22CALL TO ACTION / KEY TAKE A WAYS
related talks
41mChallenges Around Long-Term Kernel Maintenance
39mThe Life of a Kernel Bugfix
26mGetting Started With Kernel Programming: The Linux Kernel Mentorship Program
45mBeyond the Demo Kernel: Mapping BSPs to Mainline
25mLinux: Where Are We Going
50mMaintaining a Real Time Stable Kernel
30mRHEL Kernel Workflow using GitLab
19mUpstream kernel CI using patchew and TDC