From: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
To: Ye Liu <ye.liu@linux.dev>
Cc: akpm@linux-foundation.org, nao.horiguchi@gmail.com,
linmiaohe@huawei.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, Liam.Howlett@oracle.com, david@redhat.com,
harry.yoo@oracle.com, riel@surriel.com, vbabka@suse.cz,
liuye@kylinos.cn
Subject: Re: [PATCH v2 1/2] mm/rmap: rename page__anon_vma to page_anon_vma for consistency
Date: Fri, 18 Apr 2025 11:00:13 +0100 [thread overview]
Message-ID: <7ec4f1f3-a059-4be3-a02c-81281daa18b5@lucifer.local> (raw)
In-Reply-To: <20250418095600.721989-2-ye.liu@linux.dev>
On Fri, Apr 18, 2025 at 05:55:59PM +0800, Ye Liu wrote:
> From: Ye Liu <liuye@kylinos.cn>
>
> Renamed local variable page__anon_vma in page_address_in_vma() to
> page_anon_vma. The previous naming convention of using double underscores
> (__) is unnecessary and inconsistent with typical kernel style, which uses
> single underscores to denote local variables. Also updated comments to
> reflect the new variable name.
>
> Functionality unchanged.
>
> Signed-off-by: Ye Liu <liuye@kylinos.cn>
For future reference, if you don't change the patch substantially, it's best
practice to propagate the tags you already received :) that way it should just
get taken!
Anyway for avoidance of doubt:
Reviewed-by: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
> ---
> mm/rmap.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/mm/rmap.c b/mm/rmap.c
> index 67bb273dfb80..b509c226e50d 100644
> --- a/mm/rmap.c
> +++ b/mm/rmap.c
> @@ -789,13 +789,13 @@ unsigned long page_address_in_vma(const struct folio *folio,
> const struct page *page, const struct vm_area_struct *vma)
> {
> if (folio_test_anon(folio)) {
> - struct anon_vma *page__anon_vma = folio_anon_vma(folio);
> + struct anon_vma *page_anon_vma = folio_anon_vma(folio);
> /*
> * Note: swapoff's unuse_vma() is more efficient with this
> * check, and needs it to match anon_vma when KSM is active.
> */
> - if (!vma->anon_vma || !page__anon_vma ||
> - vma->anon_vma->root != page__anon_vma->root)
> + if (!vma->anon_vma || !page_anon_vma ||
> + vma->anon_vma->root != page_anon_vma->root)
> return -EFAULT;
> } else if (!vma->vm_file) {
> return -EFAULT;
> @@ -803,7 +803,7 @@ unsigned long page_address_in_vma(const struct folio *folio,
> return -EFAULT;
> }
>
> - /* KSM folios don't reach here because of the !page__anon_vma check */
> + /* KSM folios don't reach here because of the !page_anon_vma check */
> return vma_address(vma, page_pgoff(folio, page), 1);
> }
>
> --
> 2.25.1
>
next prev parent reply other threads:[~2025-04-18 10:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-18 9:55 [PATCH v2 0/2] mm: minor cleanups in rmap Ye Liu
2025-04-18 9:55 ` [PATCH v2 1/2] mm/rmap: rename page__anon_vma to page_anon_vma for consistency Ye Liu
2025-04-18 10:00 ` Lorenzo Stoakes [this message]
2025-04-18 10:12 ` Ye Liu
2025-04-18 10:40 ` David Hildenbrand
2025-04-18 10:50 ` Lorenzo Stoakes
2025-04-18 10:58 ` David Hildenbrand
2025-04-18 9:56 ` [PATCH v2 2/2] mm/rmap: fix typo in comment in page_address_in_vma Ye Liu
2025-04-18 10:00 ` 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=7ec4f1f3-a059-4be3-a02c-81281daa18b5@lucifer.local \
--to=lorenzo.stoakes@oracle.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=harry.yoo@oracle.com \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liuye@kylinos.cn \
--cc=nao.horiguchi@gmail.com \
--cc=riel@surriel.com \
--cc=vbabka@suse.cz \
--cc=ye.liu@linux.dev \
/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