Skip to contentSkip to conversation

Documentation: memory - fix warning

PATCH In review Lothar Rubusch 2 participants 2 messages Apr 7, 2020

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

PATCH v2 1/1 Documentation: memory - fix warning

Running Sphinx v1.8.4 the following warning can be seen.

$ make htmldocs &> htmldocs.log
(...)
writing output... [ 16%] block/request .. crypto/api-akcipher
./include/linux/slab.h:503: WARNING: undefined label: memory-allocation
 (if the link has no caption the label must precede a section header)
writing output... [ 19%] crypto/api-digest .. driver-api/dmaengine/client
(...)

This patch fixes the above warning.

---
 include/linux/slab.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
include/linux/slab.h +1 -1
index 03a389358562..6d454886bcaf 100644
@@ -501,7 +501,7 @@ static __always_inline void *kmalloc_large(size_t size, gfp_t flags)
  * :ref:`Documentation/core-api/mm-api.rst <mm-api-gfp-flags>`
  *
  * The recommended usage of the @flags is described at
- * :ref:`Documentation/core-api/memory-allocation.rst <memory-allocation>`
+ * :ref:`Documentation/core-api/memory-allocation.rst <memory_allocation>`
  *
  * Below is a brief outline of the most useful GFP flags
  *
Signature · 1 line
2.20.1
reviewer Acked-by on v2 1/1
#1 lore raw
Quoted 10 lines · Lothar Rubusch

Running Sphinx v1.8.4 the following warning can be seen.

$ make htmldocs &> htmldocs.log
(...)
writing output... [ 16%] block/request .. crypto/api-akcipher
./include/linux/slab.h:503: WARNING: undefined label: memory-allocation
 (if the link has no caption the label must precede a section header)
writing output... [ 19%] crypto/api-digest .. driver-api/dmaengine/client
(...)
Quoted 3 lines

This patch fixes the above warning.

Looks good. Thanks.

Quoted 18 lines
---
 include/linux/slab.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
include/linux/slab.h +1 -1
index 03a389358562..6d454886bcaf 100644
@@ -501,7 +501,7 @@ static __always_inline void *kmalloc_large(size_t size, gfp_t flags)
  * :ref:`Documentation/core-api/mm-api.rst <mm-api-gfp-flags>`
  *
  * The recommended usage of the @flags is described at
- * :ref:`Documentation/core-api/memory-allocation.rst <memory-allocation>`
+ * :ref:`Documentation/core-api/memory-allocation.rst <memory_allocation>`
  *
  * Below is a brief outline of the most useful GFP flags
  *
Signature · 1 line
~Randy