From: Peng Fan <peng.fan@nxp.com>
To: "akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"vbabka@suse.cz" <vbabka@suse.cz>,
"mhocko@suse.com" <mhocko@suse.com>,
"willy@infradead.org" <willy@infradead.org>,
"rppt@linux.vnet.ibm.com" <rppt@linux.vnet.ibm.com>,
"arunks@codeaurora.org" <arunks@codeaurora.org>,
"nborisov@suse.com" <nborisov@suse.com>,
"dan.j.williams@intel.com" <dan.j.williams@intel.com>,
"aryabinin@virtuozzo.com" <aryabinin@virtuozzo.com>,
"ldr709@gmail.com" <ldr709@gmail.com>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"van.freenix@gmail.com" <van.freenix@gmail.com>,
Peng Fan <peng.fan@nxp.com>
Subject: [PATCH] mm: __pagevec_lru_add_fn: typo fix
Date: Tue, 2 Apr 2019 09:43:31 +0000 [thread overview]
Message-ID: <20190402095609.27181-1-peng.fan@nxp.com> (raw)
There is no function named munlock_vma_pages, correct it to
munlock_vma_page.
Signed-off-by: Peng Fan <peng.fan@nxp.com>
---
mm/swap.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/mm/swap.c b/mm/swap.c
index 301ed4e04320..3a75722e68a9 100644
--- a/mm/swap.c
+++ b/mm/swap.c
@@ -867,7 +867,7 @@ static void __pagevec_lru_add_fn(struct page *page, struct lruvec *lruvec,
SetPageLRU(page);
/*
* Page becomes evictable in two ways:
- * 1) Within LRU lock [munlock_vma_pages() and __munlock_pagevec()].
+ * 1) Within LRU lock [munlock_vma_page() and __munlock_pagevec()].
* 2) Before acquiring LRU lock to put the page to correct LRU and then
* a) do PageLRU check with lock [check_move_unevictable_pages]
* b) do PageLRU check before lock [clear_page_mlock]
--
2.16.4
next reply other threads:[~2019-04-02 9:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-02 9:43 Peng Fan [this message]
2019-04-03 7:45 ` Vlastimil Babka
2019-04-04 7:30 ` Mukesh Ojha
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=20190402095609.27181-1-peng.fan@nxp.com \
--to=peng.fan@nxp.com \
--cc=akpm@linux-foundation.org \
--cc=arunks@codeaurora.org \
--cc=aryabinin@virtuozzo.com \
--cc=dan.j.williams@intel.com \
--cc=ldr709@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=nborisov@suse.com \
--cc=rppt@linux.vnet.ibm.com \
--cc=van.freenix@gmail.com \
--cc=vbabka@suse.cz \
--cc=willy@infradead.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