summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTobin C. Harding <tobin@kernel.org>2019-04-09 10:43:59 +1000
committerJonathan Corbet <corbet@lwn.net>2019-04-09 15:21:17 -0600
commit66e9c46c5cdbd9767d730c88049e1ef0438f749a (patch)
treef4b799f24645c1d0ef47b76039d73dbfe618583c
parent8c1007fdc71fdf993885d47ad17d9cc0e0b97b1c (diff)
docs: Use reference to link to rst file
Current document includes the path to an RST doc file. Since this is an RST file we can make this a link. Keeps the path as the link title since that what the original author wrote. Use reference to link to rst file. Signed-off-by: Tobin C. Harding <tobin@kernel.org> Signed-off-by: Jonathan Corbet <corbet@lwn.net>
-rw-r--r--Documentation/vm/numa.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/vm/numa.rst b/Documentation/vm/numa.rst
index 185d8a568168..5cae13e9a08b 100644
--- a/Documentation/vm/numa.rst
+++ b/Documentation/vm/numa.rst
@@ -109,8 +109,8 @@ System administrators and application designers can restrict a task's migration
to improve NUMA locality using various CPU affinity command line interfaces,
such as taskset(1) and numactl(1), and program interfaces such as
sched_setaffinity(2). Further, one can modify the kernel's default local
-allocation behavior using Linux NUMA memory policy.
-[see Documentation/admin-guide/mm/numa_memory_policy.rst.]
+allocation behavior using Linux NUMA memory policy. [see
+:ref:`Documentation/admin-guide/mm/numa_memory_policy.rst <numa_memory_policy>`].
System administrators can restrict the CPUs and nodes' memories that a non-
privileged user can specify in the scheduling or NUMA commands and functions