Documentation subsystem maintainer entry profile¶
The documentation “subsystem” is the central coordinating point for thekernel’s documentation and associated infrastructure. It covers thehierarchy under Documentation/ (with the exception ofDocumentation/devicetree), various utilities under scripts/ and, at leastsome of the time, LICENSES/.
It’s worth noting, though, that the boundaries of this subsystem are ratherfuzzier than normal. Many other subsystem maintainers like to keep controlof portions of Documentation/, and many more freely apply changes therewhen it is convenient. Beyond that, much of the kernel’s documentation isfound in the source as kerneldoc comments; those are usually (but notalways) maintained by the relevant subsystem maintainer.
The mailing list for documentation islinux-doc@vger.kernel.org. Patchesshould be made against the docs-next tree whenever possible.
Submit checklist addendum¶
When making documentation changes, you should actually build thedocumentation and ensure that no new errors or warnings have beenintroduced. Generating HTML documents and looking at the result will helpto avoid unsightly misunderstandings about how things will be rendered.
Key cycle dates¶
Patches can be sent anytime, but response will be slower than usual duringthe merge window. The docs tree tends to close late before the mergewindow opens, since the risk of regressions from documentation patches islow.
Review cadence¶
I am the sole maintainer for the documentation subsystem, and I am doingthe work on my own time, so the response to patches will occasionally beslow. I try to always send out a notification when a patch is merged (orwhen I decide that one cannot be). Do not hesitate to send a ping if youhave not heard back within a week of sending a patch.