From: Ye Liu <ye.liu@linux.dev>
To: akpm@linux-foundation.org, linmiaohe@huawei.com, nao.horiguchi@gmail.com
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Ye Liu <liuye@kylinos.cn>
Subject: [PATCH 2/3] mm/rmap: fix typo in comment in page_address_in_vma
Date: Fri, 18 Apr 2025 15:52:25 +0800 [thread overview]
Message-ID: <20250418075226.695014-3-ye.liu@linux.dev> (raw)
In-Reply-To: <20250418075226.695014-1-ye.liu@linux.dev>
From: Ye Liu <liuye@kylinos.cn>
Fixes a minor typo in the comment above page_address_in_vma():
"responsibililty" → "responsibility"
Signed-off-by: Ye Liu <liuye@kylinos.cn>
---
mm/rmap.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/mm/rmap.c b/mm/rmap.c
index b509c226e50d..a9eed8981e18 100644
--- a/mm/rmap.c
+++ b/mm/rmap.c
@@ -774,7 +774,7 @@ static bool should_defer_flush(struct mm_struct *mm, enum ttu_flags flags)
* @vma: The VMA we need to know the address in.
*
* Calculates the user virtual address of this page in the specified VMA.
- * It is the caller's responsibililty to check the page is actually
+ * It is the caller's responsibility to check the page is actually
* within the VMA. There may not currently be a PTE pointing at this
* page, but if a page fault occurs at this address, this is the page
* which will be accessed.
--
2.25.1
next prev parent reply other threads:[~2025-04-18 7:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-18 7:52 [PATCH 0/3] mm: minor cleanups in rmap and memory-failure Ye Liu
2025-04-18 7:52 ` [PATCH 1/3] mm/rmap: rename page__anon_vma to page_anon_vma for consistency Ye Liu
2025-04-18 9:14 ` Lorenzo Stoakes
2025-04-18 9:37 ` Harry Yoo
2025-04-18 9:42 ` Lorenzo Stoakes
2025-04-18 7:52 ` Ye Liu [this message]
2025-04-18 9:14 ` [PATCH 2/3] mm/rmap: fix typo in comment in page_address_in_vma Lorenzo Stoakes
2025-04-18 7:52 ` [PATCH 3/3] mm/memory-failure: inline add_to_kill_anon_file() logic at call sites Ye Liu
2025-04-18 9:18 ` Lorenzo Stoakes
2025-04-18 9:12 ` [PATCH 0/3] mm: minor cleanups in rmap and memory-failure Lorenzo Stoakes
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=20250418075226.695014-3-ye.liu@linux.dev \
--to=ye.liu@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liuye@kylinos.cn \
--cc=nao.horiguchi@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.