From: Deming Wang Date: Wed, 18 Jan 2023 02:54:03 +0000 (-0500) Subject: Documentation: mm: use `s/higmem/highmem/` fix typo for highmem X-Git-Tag: v6.6.17~5460^2~217 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=d0634a622be35df2dfa80dc14ee1482ae1889cb2;p=platform%2Fkernel%2Flinux-rpi.git Documentation: mm: use `s/higmem/highmem/` fix typo for highmem We should use highmem replace higmem. Link: https://lkml.kernel.org/r/20230118025403.1531-1-wangdeming@inspur.com Signed-off-by: Deming Wang Reviewed-by: Ira Weiny Cc: "Fabio M. De Francesco" Cc: Jonathan Corbet Cc: Mike Rapoport (IBM) Cc: Sebastian Andrzej Siewior Signed-off-by: Andrew Morton --- diff --git a/Documentation/mm/highmem.rst b/Documentation/mm/highmem.rst index e691a06..4503868 100644 --- a/Documentation/mm/highmem.rst +++ b/Documentation/mm/highmem.rst @@ -83,7 +83,7 @@ list shows them in order of preference of use. for pages which are known to not come from ZONE_HIGHMEM. However, it is always safe to use kmap_local_page() / kunmap_local(). - While it is significantly faster than kmap(), for the higmem case it + While it is significantly faster than kmap(), for the highmem case it comes with restrictions about the pointers validity. Contrary to kmap() mappings, the local mappings are only valid in the context of the caller and cannot be handed to other contexts. This implies that users must