[PATCH v2 3/4] docs: Remove unnecessary reference link title

From: Tobin C. Harding
Date: Mon Apr 08 2019 - 20:44:49 EST

Labels that precede a heading use the heading as the link title.
Explicitly adding the link title is redundant and makes the reference
slightly less maintainable.

Remove unnecessary reference link title.

Signed-off-by: Tobin C. Harding <tobin@xxxxxxxxxx>
Documentation/admin-guide/mm/numa_memory_policy.rst | 9 ++++-----
1 file changed, 4 insertions(+), 5 deletions(-)

diff --git a/Documentation/admin-guide/mm/numa_memory_policy.rst b/Documentation/admin-guide/mm/numa_memory_policy.rst
index d78c5b315f72..1ef0146eaa4d 100644
--- a/Documentation/admin-guide/mm/numa_memory_policy.rst
+++ b/Documentation/admin-guide/mm/numa_memory_policy.rst
@@ -20,8 +20,7 @@ which is an administrative mechanism for restricting the nodes from which
memory may be allocated by a set of processes. Memory policies are a
programming interface that a NUMA-aware application can take advantage of. When
both cpusets and policies are applied to a task, the restrictions of the cpuset
-takes priority. See :ref:`Memory Policies and cpusets <mem_pol_and_cpusets>`
-below for more details.
+takes priority. See :ref:`mem_pol_and_cpusets` below for more details.

Memory Policy Concepts
@@ -56,7 +55,7 @@ Task/Process Policy
[clone() w/o the CLONE_VM flag] and exec*(). This allows a parent task
to establish the task policy for a child task exec()'d from an
executable image that has no awareness of memory policy. See the
- :ref:`Memory Policy APIs <memory_policy_apis>` section,
+ :ref:`memory_policy_apis` section,
below, for an overview of the system call
that a task may use to set/change its task/process policy.

@@ -77,7 +76,7 @@ VMA Policy
A "VMA" or "Virtual Memory Area" refers to a range of a task's
virtual address space. A task may define a specific policy for a range
of its virtual address space. See the
- :ref:`Memory Policy APIs <memory_policy_apis>` section,
+ :ref:`memory_policy_apis` section,
below, for an overview of the mbind() system call used to set a VMA

@@ -142,7 +141,7 @@ Shared Policy
Although hugetlbfs segments now support lazy allocation, their support
for shared policy has not been completed.

- As mentioned above in :ref:`VMA policies <vma_policy>` section,
+ As mentioned above in :ref:`vma_policy` section,
allocations of page cache pages for regular files mmap()ed
with MAP_SHARED ignore any VMA policy installed on the virtual
address range backed by the shared file mapping. Rather,