The patch titled Subject: Documentation: mm: use `s/higmem/highmem/` fix typo for highmem has been added to the -mm mm-unstable branch. Its filename is documentation-mm-use-s-higmem-highmem-fix-typo-for-highmem.patch This patch will shortly appear at https://git.kernel.org/pub/scm/linux/kernel/git/akpm/25-new.git/tree/patches/documentation-mm-use-s-higmem-highmem-fix-typo-for-highmem.patch This patch will later appear in the mm-unstable branch at git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm Before you just go and hit "reply", please: a) Consider who else should be cc'ed b) Prefer to cc a suitable mailing list as well c) Ideally: find the original patch on the mailing list and do a reply-to-all to that, adding suitable additional cc's *** Remember to use Documentation/process/submit-checklist.rst when testing your code *** The -mm tree is included into linux-next via the mm-everything branch at git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm and is updated there every 2-3 working days ------------------------------------------------------ From: Deming Wang <wangdeming@xxxxxxxxxx> Subject: Documentation: mm: use `s/higmem/highmem/` fix typo for highmem Date: Tue, 17 Jan 2023 21:54:03 -0500 We should use highmem replace higmem. Link: https://lkml.kernel.org/r/20230118025403.1531-1-wangdeming@xxxxxxxxxx Signed-off-by: Deming Wang <wangdeming@xxxxxxxxxx> Reviewed-by: Ira Weiny <ira.weiny@xxxxxxxxx> Cc: "Fabio M. De Francesco" <fmdefrancesco@xxxxxxxxx> Cc: Jonathan Corbet <corbet@xxxxxxx> Cc: Mike Rapoport (IBM) <rppt@xxxxxxxxxx> Cc: Sebastian Andrzej Siewior <bigeasy@xxxxxxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- Documentation/mm/highmem.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) --- a/Documentation/mm/highmem.rst~documentation-mm-use-s-higmem-highmem-fix-typo-for-highmem +++ a/Documentation/mm/highmem.rst @@ -83,7 +83,7 @@ list shows them in order of preference o 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 _ Patches currently in -mm which might be from wangdeming@xxxxxxxxxx are documentation-mm-use-s-higmem-highmem-fix-typo-for-highmem.patch