1.. SPDX-License-Identifier: GPL-2.0 2Documentation subsystem maintainer entry profile 3================================================ 4 5The documentation "subsystem" is the central coordinating point for the 6kernel's documentation and associated infrastructure. It covers the 7hierarchy under Documentation/ (with the exception of 8Documentation/device-tree), various utilities under scripts/ and, at least 9some of the time, LICENSES/. 10 11It's worth noting, though, that the boundaries of this subsystem are rather 12fuzzier than normal. Many other subsystem maintainers like to keep control 13of portions of Documentation/, and many more freely apply changes there 14when it is convenient. Beyond that, much of the kernel's documentation is 15found in the source as kerneldoc comments; those are usually (but not 16always) maintained by the relevant subsystem maintainer. 17 18The mailing list for documentation is linux-doc@vger.kernel.org. Patches 19should be made against the docs-next tree whenever possible. 20 21Submit checklist addendum 22------------------------- 23 24When making documentation changes, you should actually build the 25documentation and ensure that no new errors or warnings have been 26introduced. Generating HTML documents and looking at the result will help 27to avoid unsightly misunderstandings about how things will be rendered. 28 29Key cycle dates 30--------------- 31 32Patches can be sent anytime, but response will be slower than usual during 33the merge window. The docs tree tends to close late before the merge 34window opens, since the risk of regressions from documentation patches is 35low. 36 37Review cadence 38-------------- 39 40I am the sole maintainer for the documentation subsystem, and I am doing 41the work on my own time, so the response to patches will occasionally be 42slow. I try to always send out a notification when a patch is merged (or 43when I decide that one cannot be). Do not hesitate to send a ping if you 44have not heard back within a week of sending a patch. 45