Documentation: mm: use `s/higmem/highmem/` fix typo for highmem
Commit Message
We should use highmem replace higmem.
Signed-off-by: Deming Wang <wangdeming@inspur.com>
---
Documentation/mm/highmem.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Comments
Deming Wang wrote:
> We should use highmem replace higmem.
>
> Signed-off-by: Deming Wang <wangdeming@inspur.com>
Reviewed-by: Ira Weiny <ira.weiny@intel.com>
> ---
> Documentation/mm/highmem.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/mm/highmem.rst b/Documentation/mm/highmem.rst
> index 59d1078f53df..7da4a0d175f0 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
> --
> 2.27.0
>
@@ -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