From: Lothar Rubusch <l.rubusch@gmail.com>
To: corbet@lwn.net, rdunlap@infradead.org
Cc: linux-doc@vger.kernel.org, Lothar Rubusch <l.rubusch@gmail.com>
Subject: [PATCH v2] Documentation: memory - fix warning
Date: Tue, 7 Apr 2020 22:34:55 +0000 [thread overview]
Message-ID: <20200407223455.14027-1-l.rubusch@gmail.com> (raw)
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.
Signed-off-by: Lothar Rubusch <l.rubusch@gmail.com>
---
include/linux/slab.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/linux/slab.h b/include/linux/slab.h
index 03a389358562..6d454886bcaf 100644
--- a/include/linux/slab.h
+++ b/include/linux/slab.h
@@ -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
*
--
2.20.1
next reply other threads:[~2020-04-07 22:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-07 22:34 Lothar Rubusch [this message]
2020-04-07 22:49 ` [PATCH v2] Documentation: memory - fix warning Randy Dunlap
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200407223455.14027-1-l.rubusch@gmail.com \
--to=l.rubusch@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=rdunlap@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).