On Tue, Jan 17, 2023 at 07:43:56PM -0500, Deming Wang wrote: > Substitute occurrencies of "higmem" with "highmem". > > Signed-off-by: Deming Wang <wangdeming@xxxxxxxxxx> > --- > 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 Are you sure you have seen the other occurences of higmem in the same doc? If so, do s/higmem/highmem/g. Also, the patch subject prefix should have been Documentation: mm: highmem, and also s/mistakeo/mistake/ in the subject. Thanks. -- An old man doll... just what I always wanted! - Clara
Attachment:
signature.asc
Description: PGP signature