You May Be a Linux Kernel Maintainer - and Not Know It

This presentation explains how contributors become Linux kernel maintainers and the responsibilities involved in maintaining drivers. It covers maintainer roles, patch review and testing, upstream workflows, time expectations, and available resources.

Syllabus

Intro
A Real Life Story
New driver is accepted
What happens next?
A 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
driver maintainer - patch path?
driver maintainer - possible roles
Ignore role
Advise upstream maintainer
Review patches
Sub-maintainer
Some Maintainer Tasks
Your Role summarized Participate in the tow of a patch from developers to the upstream maintainer
Signed-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
Tested-by How should patches be tested?
Time expectations
Bonus Points Monitor or skim your subsystem mais