mm: fix some spelling mistakes in comments

Fix some spelling mistakes in comments:
	udpate ==> update
	succesful ==> successful
	exmaple ==> example
	unneccessary ==> unnecessary
	stoping ==> stopping
	uknown ==> unknown

Link: https://lkml.kernel.org/r/20201127011747.86005-1-shihaitao1@huawei.com
Signed-off-by: Haitao Shi <shihaitao1@huawei.com>
Reviewed-by: Mike Rapoport <rppt@linux.ibm.com>
Reviewed-by: Souptick Joarder <jrdr.linux@gmail.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

diff --git a/mm/filemap.c b/mm/filemap.c
index c178022d78935bebefc76f99d7fd0f609f1f0771..2e16daf98bf91cc7fe5008fea6c811dd96c4d3dd 100644 (file)
--- a/mm/filemap.c
+++ b/mm/filemap.c
@@ -1359,7 +1359,7 @@ static int __wait_on_page_locked_async(struct page *page,
        else
                ret = PageLocked(page);
        /*
-        * If we were succesful now, we know we're still on the
+        * If we were successful now, we know we're still on the
         * waitqueue as we're still under the lock. This means it's
         * safe to remove and return success, we know the callback
         * isn't going to trigger.

diff --git a/mm/huge_memory.c b/mm/huge_memory.c
index 1efe2b5ad59af029450de97f0d43a8a0e6fb2cb8..9237976abe72b7a7aa6afe50fce36c0b34007939 100644 (file)
--- a/mm/huge_memory.c
+++ b/mm/huge_memory.c
@@ -2391,7 +2391,7 @@ static void __split_huge_page_tail(struct page *head, int tail,
         * Clone page flags before unfreezing refcount.
         *
         * After successful get_page_unless_zero() might follow flags change,
-        * for exmaple lock_page() which set PG_waiters.
+        * for example lock_page() which set PG_waiters.
         */
        page_tail->flags &= ~PAGE_FLAGS_CHECK_AT_PREP;
        page_tail->flags |= (head->flags &

diff --git a/mm/khugepaged.c b/mm/khugepaged.c
index ad316d2e1fee50b136cf10082397b1869b629a4d..67ab391a537393251b22591a310118f76525438d 100644 (file)
--- a/mm/khugepaged.c
+++ b/mm/khugepaged.c
@@ -1275,7 +1275,7 @@ static int khugepaged_scan_pmd(struct mm_struct *mm,
                         * PTEs are armed with uffd write protection.
                         * Here we can also mark the new huge pmd as
                         * write protected if any of the small ones is
-                        * marked but that could bring uknown
+                        * marked but that could bring unknown
                         * userfault messages that falls outside of
                         * the registered range.  So, just be simple.
                         */

diff --git a/mm/memblock.c b/mm/memblock.c
index 049df4163a976c84460b6a269725f9454b58dd92..a3c406070f4d6f0db93da521885e2428bc7fae21 100644 (file)
--- a/mm/memblock.c
+++ b/mm/memblock.c
@@ -871,7 +871,7 @@ int __init_memblock memblock_physmem_add(phys_addr_t base, phys_addr_t size)
  * @base: base address of the region
  * @size: size of the region
  * @set: set or clear the flag
- * @flag: the flag to udpate
+ * @flag: the flag to update
  *
  * This function isolates region [@base, @base + @size), and sets/clears flag
  *

diff --git a/mm/migrate.c b/mm/migrate.c
index ee802cb509a3f425fc6884fe0930b506787dfd4f..ee5e612b4cd87bcab7b72948bee803d4fb346615 100644 (file)
--- a/mm/migrate.c
+++ b/mm/migrate.c
@@ -2594,7 +2594,7 @@ static bool migrate_vma_check_page(struct page *page)
                 * will bump the page reference count. Sadly there is no way to
                 * differentiate a regular pin from migration wait. Hence to
                 * avoid 2 racing thread trying to migrate back to CPU to enter
-                * infinite loop (one stoping migration because the other is
+                * infinite loop (one stopping migration because the other is
                 * waiting on pte migration entry). We always return true here.
                 *
                 * FIXME proper solution is to rework migration_entry_wait() so

diff --git a/mm/page_ext.c b/mm/page_ext.c
index 16b161f28a31d974bc7651c5ae4a0af9ee6b9637..df6f74aac8e155df57be7015f4eec86a91434d33 100644 (file)
--- a/mm/page_ext.c
+++ b/mm/page_ext.c
@@ -34,7 +34,7 @@
  *
  * The need callback is used to decide whether extended memory allocation is
  * needed or not. Sometimes users want to deactivate some features in this
- * boot and extra memory would be unneccessary. In this case, to avoid
+ * boot and extra memory would be unnecessary. In this case, to avoid
  * allocating huge chunk of memory, each clients represent their need of
  * extra memory through the need callback. If one of the need callbacks
  * returns true, it means that someone needs extra memory so that