path: root/Documentation/core-api
diff options
authorNicholas Piggin <>2021-04-29 22:59:01 -0700
committerLinus Torvalds <>2021-04-30 11:20:40 -0700
commit4ad0ae8c64ac8f81a3651bca11be7c3cb086df80 (patch)
treecfeb318f03b88d8b4f8d4a110b894c40a1be7ea4 /Documentation/core-api
parent94f88d7b901c28210d196f38168a548950dfc607 (diff)
mm/vmalloc: remove unmap_kernel_range
This is a shim around vunmap_range, get rid of it. Move the main API comment from the _noflush variant to the normal variant, and make _noflush internal to mm/. [ fix nommu builds and a comment bug per sfr] Link: [ move vunmap_range_noflush() stub inside !CONFIG_MMU, not !CONFIG_NUMA] [ fix nommu builds] Link: Link: Signed-off-by: Nicholas Piggin <> Reviewed-by: Christoph Hellwig <> Cc: C├ędric Le Goater <> Cc: Uladzislau Rezki <> Signed-off-by: Andrew Morton <> Signed-off-by: Linus Torvalds <>
Diffstat (limited to 'Documentation/core-api')
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/core-api/cachetlb.rst b/Documentation/core-api/cachetlb.rst
index 756f7bcf8191..fe4290e26729 100644
--- a/Documentation/core-api/cachetlb.rst
+++ b/Documentation/core-api/cachetlb.rst
@@ -215,7 +215,7 @@ Here are the routines, one by one:
The first of these two routines is invoked after vmap_range()
has installed the page table entries. The second is invoked
- before unmap_kernel_range() deletes the page table entries.
+ before vunmap_range() deletes the page table entries.
There exists another whole class of cpu cache issues which currently
require a whole different set of interfaces to handle properly.