From: Hyeonggon Yoo <42.hyeyoo@gmail.com>
To: akpm@linux-foundation.org
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Hyeonggon Yoo <42.hyeyoo@gmail.com>
Subject: [PATCH] mm: fix typos in comments
Date: Sun, 9 May 2021 15:26:00 +0900 [thread overview]
Message-ID: <20210509062600.23860-1-42.hyeyoo@gmail.com> (raw)
tha -> that in mm/swap.c
statments -> statements in include/linux/mm.h
Signed-off-by: Hyeonggon Yoo <42.hyeyoo@gmail.com>
---
include/linux/mm.h | 2 +-
mm/swap.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/include/linux/mm.h b/include/linux/mm.h
index 322ec61d0da7..ea074f7a9d0c 100644
--- a/include/linux/mm.h
+++ b/include/linux/mm.h
@@ -155,7 +155,7 @@ extern int mmap_rnd_compat_bits __read_mostly;
/* This function must be updated when the size of struct page grows above 80
* or reduces below 56. The idea that compiler optimizes out switch()
* statement, and only leaves move/store instructions. Also the compiler can
- * combine write statments if they are both assignments and can be reordered,
+ * combine write statements if they are both assignments and can be reordered,
* this can result in several of the writes here being dropped.
*/
#define mm_zero_struct_page(pp) __mm_zero_struct_page(pp)
diff --git a/mm/swap.c b/mm/swap.c
index dfb48cf9c2c9..a1c9d23ef635 100644
--- a/mm/swap.c
+++ b/mm/swap.c
@@ -554,7 +554,7 @@ static void lru_deactivate_file_fn(struct page *page, struct lruvec *lruvec)
} else {
/*
* The page's writeback ends up during pagevec
- * We moves tha page into tail of inactive.
+ * We moves that page into tail of inactive.
*/
add_page_to_lru_list_tail(page, lruvec);
__count_vm_events(PGROTATED, nr_pages);
--
2.25.1
next reply other threads:[~2021-05-09 6:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-09 6:26 Hyeonggon Yoo [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-03-18 10:37 [PATCH] mm: fix typos in comments Julia Lawall
2022-03-18 11:07 ` Joe Perches
2022-03-18 11:15 ` Julia Lawall
2021-03-22 2:51 [PATCH] mm: Fix " Ingo Molnar
2021-03-22 3:44 ` Matthew Wilcox
2021-03-22 3:52 ` Randy Dunlap
2021-03-22 3:58 ` Bhaskar Chowdhury
2021-03-22 4:01 ` Randy Dunlap
2021-03-22 20:50 ` Ingo Molnar
2021-03-22 21:02 ` Randy Dunlap
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210509062600.23860-1-42.hyeyoo@gmail.com \
--to=42.hyeyoo@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).