From: Lothar Rubusch <l.rubusch@gmail.com>
To: corbet@lwn.net
Cc: linux-doc@vger.kernel.org, Lothar Rubusch <l.rubusch@gmail.com>
Subject: [PATCH] Documentation: memory - fix warning
Date: Mon, 6 Apr 2020 22:07:43 +0000 [thread overview]
Message-ID: <20200406220743.22183-1-l.rubusch@gmail.com> (raw)
The label in sphinx can refer to a document section but not to the document
header.
The handle 'memory_allocation' is used in another document(s) to refer to
GFP_KERNEL flags description in this modified document.
Since the sphinx label does not work as it is placed here, a proposal is to
better shift it to the section about memory allocation flags.
Signed-off-by: Lothar Rubusch <l.rubusch@gmail.com>
---
Documentation/core-api/memory-allocation.rst | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/Documentation/core-api/memory-allocation.rst b/Documentation/core-api/memory-allocation.rst
index 4aa82ddd01b8..4d66ddcb9883 100644
--- a/Documentation/core-api/memory-allocation.rst
+++ b/Documentation/core-api/memory-allocation.rst
@@ -1,5 +1,3 @@
-.. _memory_allocation:
-
=======================
Memory Allocation Guide
=======================
@@ -26,6 +24,9 @@ answer, although very likely you should use
Of course there are cases when other allocation APIs and different GFP
flags must be used.
+
+.. _memory_allocation:
+
Get Free Page flags
===================
--
2.20.1
next reply other threads:[~2020-04-06 22:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-06 22:07 Lothar Rubusch [this message]
2020-04-07 19:24 ` [PATCH] Documentation: memory - fix warning Jonathan Corbet
2020-04-07 22:09 ` Lothar Rubusch
2020-04-07 22:21 ` 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=20200406220743.22183-1-l.rubusch@gmail.com \
--to=l.rubusch@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.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).