You may be a Linux Kernel Maintainer - and Not Know It!
summary
Adding a name to MAINTAINERS effectively makes that engineer a kernel maintainer overnight, and patches can either bypass them to subsystem maintainers or flow through them for review and signed-off-by attribution. Five practical involvement levels range from ignore the role to becoming a submaintainer who enforces architecture, testing and performance data. Required checks include checkpatch, make W= warnings, sparse/smatch, hardware boot tests and a clear bug pointer for Cc: stable consideration. Time commitment and handoffs to upstream must be negotiated.
AI-written summary · about
chapters (17)
- 0:00Intro
- 0:21A Real Life Story
- 0:47New driver is accepted
- 1:32What happens next?
- 2:03A gap in our internal OSS training We had helped our development team learn how to submit a driver to the Linux kernel But we had not prepared them for what involved in being a maintainer of the driver
- 2:28driver maintainer - patch path?
- 3:34driver maintainer - possible roles
- 4:23Ignore role
- 5:03Advise upstream maintainer
- 7:25Review patches
- 10:11Sub-maintainer
- 11:10Some Maintainer Tasks
- 14:49Your Role summarized Participate in the tow of a patch from developers to the upstream maintainer
- 16:03Signed-off-by: - Developer's tag must exist in paich -If the patchows through the driver maintainer tree, with a pull request to the subsystem maintainer, then the driver maintainer adds
- 18:35Tested-by How should patches be tested?
- 23:27Time expectations
- 24:34Bonus Points Monitor or skim your subsystem mais
related talks
38mGuide To Become Linux Kernel Maintainer
45mFrom an Idea to a Patch in the Linux Mainline
01h 27mMeet the Maintainers: Discuss Roles and Responsibilities, Areas of Improvements and...
07mWhat's a Maintainer Anyway?
47mTrying to Explain the 'Incomprehensible' Decision Making Process of a Subsystem Maintainer
39mGuiding Newcomers: A Mentor’s Journey Through Linux Kernel Development
39mThe Life of a Kernel Bugfix
56mMaintainer_s Diary - We Have a Scaling Problem
