[merged mm-stable] documentation-mm-use-s-higmem-highmem-fix-typo-for-highmem.patch removed from -mm tree

[merged mm-stable] documentation-mm-use-s-higmem-highmem-fix-typo-for-highmem.patch removed from -mm tree

[Andrew Morton]

The quilt patch titled
     Subject: Documentation: mm: use `s/higmem/highmem/` fix typo for highmem
has been removed from the -mm tree.  Its filename was
     documentation-mm-use-s-higmem-highmem-fix-typo-for-highmem.patch

This patch was dropped because it was merged into the mm-stable branch
of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm

------------------------------------------------------
From: Deming Wang <wangdeming@inspur.com>
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@inspur.com
Signed-off-by: Deming Wang <wangdeming@inspur.com>
Reviewed-by: Ira Weiny <ira.weiny@intel.com>
Cc: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
Cc: Jonathan Corbet <corbet@lwn.net>
Cc: Mike Rapoport (IBM) <rppt@kernel.org>
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---


--- 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@inspur.com are