diff options
| author | Lukas Bulwahn <lukas.bulwahn@gmail.com> | 2020-01-18 16:36:20 +0100 |
|---|---|---|
| committer | Jonathan Corbet <corbet@lwn.net> | 2020-01-24 17:54:42 +0100 |
| commit | 06b9c269938ba1e9356b74584cd1ff738c0cf4de (patch) | |
| tree | bac68f930748d9fa39948826205a8136589a5fd1 | |
| parent | zram: correct documentation about sysfs node of huge page writeback (diff) | |
| download | linux-06b9c269938ba1e9356b74584cd1ff738c0cf4de.tar.xz linux-06b9c269938ba1e9356b74584cd1ff738c0cf4de.zip | |
docs: nvdimm: use ReST notation for subsection
The ACPI Device Specific Methods (_DSM) paragraph is intended to be a
subsection of the Submit Checklist Addendum section. Dan Williams however
used Markdown notation for this subsection, which does not parse as
intended in a ReST documentation.
Change the markup to ReST notation, as described in the Specific
guidelines for the kernel documentation section in
Documentation/doc-guide/sphinx.rst.
Fixes: 47843401e3a0 ("libnvdimm, MAINTAINERS: Maintainer Entry Profile")
Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Link: https://lore.kernel.org/r/20200118153620.8276-1-lukas.bulwahn@gmail.com
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
| -rw-r--r-- | Documentation/nvdimm/maintainer-entry-profile.rst | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/Documentation/nvdimm/maintainer-entry-profile.rst b/Documentation/nvdimm/maintainer-entry-profile.rst index 77081fd9be95..efe37adadcea 100644 --- a/Documentation/nvdimm/maintainer-entry-profile.rst +++ b/Documentation/nvdimm/maintainer-entry-profile.rst @@ -33,7 +33,8 @@ Those tests need to be passed before the patches go upstream, but not necessarily before initial posting. Contact the list if you need help getting the test environment set up. -### ACPI Device Specific Methods (_DSM) +ACPI Device Specific Methods (_DSM) +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Before patches enabling for a new _DSM family will be considered it must be assigned a format-interface-code from the NVDIMM Sub-team of the ACPI Specification Working Group. In general, the stance of the subsystem is |