From: Mukesh Ojha <mojha@codeaurora.org>
To: Peng Fan <peng.fan@nxp.com>,
"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>
Subject: Re: [PATCH] mm: __pagevec_lru_add_fn: typo fix
Date: Thu, 4 Apr 2019 13:00:11 +0530 [thread overview]
Message-ID: <43a2f07f-1b28-cd85-b37c-af730b446d2e@codeaurora.org> (raw)
In-Reply-To: <20190402095609.27181-1-peng.fan@nxp.com>
On 4/2/2019 3:13 PM, Peng Fan wrote:
> There is no function named munlock_vma_pages, correct it to
> munlock_vma_page.
>
> Signed-off-by: Peng Fan <peng.fan@nxp.com>
Reviewed-by: Mukesh Ojha <mojha@codeaurora.org>
Cheers,
-Mukesh
> ---
> 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]
prev parent reply other threads:[~2019-04-04 7:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-02 9:43 [PATCH] mm: __pagevec_lru_add_fn: typo fix Peng Fan
2019-04-03 7:45 ` Vlastimil Babka
2019-04-04 7:30 ` Mukesh Ojha [this message]
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=43a2f07f-1b28-cd85-b37c-af730b446d2e@codeaurora.org \
--to=mojha@codeaurora.org \
--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=peng.fan@nxp.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;
as well as URLs for NNTP newsgroup(s).