So you're a Linux kernel developer? Name all subsystems.
summary
Maintainers-file entries become vertices and share an edge when they overlap in actual lines of code; clustering (walktrap) on that section graph groups them into de‑facto subsystems rather than the 2,000+ raw MAINTAINERS sections. Top‑20 analysis exposes clear subsystems: media (with a staging and Android drivers subcluster), networking and DRM drivers, and a highly connected ARM cluster whose highest‑degree vertex is open firmware / flattened device tree bindings. Patches are labeled conforming integration or not via get_maintainer.pl, revealing examples of unconforming merges (e.g. Intel DRM/gbt drivers); results feed tooling (lfd/pasta) and ELISA safety‑certification evidence.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 1:20Motivation and Goals
- 2:20Safety Critical Certification
- 4:02Open Development Process
- 5:24Maintenance Hierarchy
- 7:20Crosscutting Patches
- 7:45The Problem
- 8:43What is a subsystem
- 9:25Media Subsystem
- 10:52Subsystem Definition
- 11:45Subsystem Detection
- 14:02Section Graph
- 15:08Section Graph Example
- 15:40Cluster Discussion
- 23:25Patch Integration
- 27:36Future work
- 36:35Disclaimer
