diff options
| author | Deming Wang <[email protected]> | 2023-01-17 21:54:03 -0500 |
|---|---|---|
| committer | Andrew Morton <[email protected]> | 2023-02-02 22:33:24 -0800 |
| commit | d0634a622be35df2dfa80dc14ee1482ae1889cb2 (patch) | |
| tree | bde1b7f95c6f44d2f6670116276f05ecd3504d83 | |
| parent | 148aa87e4f631e98d926d006604116fd2b2f3a93 (diff) | |
Documentation: mm: use `s/higmem/highmem/` fix typo for highmem
We should use highmem replace higmem.
Link: https://lkml.kernel.org/r/[email protected]
Signed-off-by: Deming Wang <[email protected]>
Reviewed-by: Ira Weiny <[email protected]>
Cc: "Fabio M. De Francesco" <[email protected]>
Cc: Jonathan Corbet <[email protected]>
Cc: Mike Rapoport (IBM) <[email protected]>
Cc: Sebastian Andrzej Siewior <[email protected]>
Signed-off-by: Andrew Morton <[email protected]>
| -rw-r--r-- | Documentation/mm/highmem.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/mm/highmem.rst b/Documentation/mm/highmem.rst index e691a06fb337..4503868b0865 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 |